Indeed the timeout is likely due to your document becoming too large so that recognition time exceeds the 60 seconds timeout.
The best way to solve the problem would be to send the document strokes incementally rather than at once and thus to use the WebSockets.
Could you please, give us some details about your use case so that we can better advice you?
Best regards,
Gwenaëlle
S
Seungchan Jo
said
over 3 years ago
I am using myscript to recognize documents after finishing writing, so I send all points of the document at once.
If there is no time constraint on the response time of websocket, websocket seems to be the proper solution.
But if not, I'll need to split points of a document up properly to receive a response in time.
But before I send it, I can't use myscript to correctly split points by letter or paragraph, so I think I have no choice but to develop a separate algorithm for properly dividing the points in the document.
I would appreciate it if you could tell me if websocket has no response time limit and if there is a time limit, if there is any other suitable solution.
G
Gwenaelle @MyScript
said
over 3 years ago
Answer
Dear Seungchan Jo,
Thank you for your update.
Web socket is better suited for taking advantage of interactivity, when strokes are continuously sent and received as users write.
What is the size of the document your are currentely processing: how many pages? how many strokes?
Seungchan Jo
I am using REST API of Interactive Ink SDK (URL : https://cloud.myscript.com/api/v4.0/iink/batch)
Because I send all points of a document at once, the API response is longer as the document grows.
If the response exceeds 60 seconds, the following error is returned.
Is there a way to solve this problem?
Dear Seungchan Jo,
Thank you for your update.
Web socket is better suited for taking advantage of interactivity, when strokes are continuously sent and received as users write.
What is the size of the document your are currentely processing: how many pages? how many strokes?
Regards,
Gwenaëlle
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstGwenaelle @MyScript
Dear Seungchan Jo,
Thank you for your request.
Indeed the timeout is likely due to your document becoming too large so that recognition time exceeds the 60 seconds timeout.
The best way to solve the problem would be to send the document strokes incementally rather than at once and thus to use the WebSockets.
Could you please, give us some details about your use case so that we can better advice you?
Best regards,
Gwenaëlle
Seungchan Jo
I am using myscript to recognize documents after finishing writing, so I send all points of the document at once.
If there is no time constraint on the response time of websocket, websocket seems to be the proper solution.
But if not, I'll need to split points of a document up properly to receive a response in time.
But before I send it, I can't use myscript to correctly split points by letter or paragraph, so I think I have no choice but to develop a separate algorithm for properly dividing the points in the document.
I would appreciate it if you could tell me if websocket has no response time limit and if there is a time limit, if there is any other suitable solution.
Gwenaelle @MyScript
Dear Seungchan Jo,
Thank you for your update.
Web socket is better suited for taking advantage of interactivity, when strokes are continuously sent and received as users write.
What is the size of the document your are currentely processing: how many pages? how many strokes?
Regards,
Gwenaëlle