Does this library handle this? Sample RPC #3

Closed
opened 2016-06-23 11:55:08 +08:00 by rjpalermo1 · 1 comment
rjpalermo1 commented 2016-06-23 11:55:08 +08:00 (Migrated from github.com)

Hello, sorry for the second post but your library has me hopeful for an answer after a long, hard day doing Google searches.

What I am reading is this library can handle an HTTP RPC call like this....

My published endpoint = https:mywebserver.com/process

can receive and process this actual endpoint:

https://webserver.com/service/Process.py?clientId=123456789&deviceId=001&userId=12334455&locationId=34

Is this correct? If so, can you give an example of how this looks in an code? I have to convert about 10 of these.

Hello, sorry for the second post but your library has me hopeful for an answer after a long, hard day doing Google searches. What I am reading is this library can handle an HTTP RPC call like this.... My published endpoint = `https:mywebserver.com/process` can receive and process this actual endpoint: `https://webserver.com/service/Process.py?clientId=123456789&deviceId=001&userId=12334455&locationId=34` Is this correct? If so, can you give an example of how this looks in an code? I have to convert about 10 of these.
gucheen commented 2016-06-23 12:41:11 +08:00 (Migrated from github.com)

FetchQL is designed for GraphQL only.
It is not suitable for the scene that you meet.

FetchQL is designed for GraphQL only. It is not suitable for the scene that you meet.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gucheen/fetchql#3
No description provided.