-
November 2nd, 2016, 01:06 PM
#11
Originally Posted by
gianluca.finocchiaro
Replacing the "raise IOError()" in the _handle_stream method is not a good idea, because a server error response while connecting is a symptom that something is not working properly, as you can read from Paragraph 4.1 of the
Network Protocol Tutorial
In fact the only error I encountered for now with IG's stream server happen here, about 3 times a day, while trying to bind. I receive a SYNC ERROR about half a second after a LOOP message, before the binding is done. In this situation the reconnection work at first try.
I understand that errors in this point should be used with care for a clean client, but for my project I believe that the only errors that can occur here are the temporary ones, which would be resolved with a later reconnection.
Originally Posted by
gianluca.finocchiaro
It is necessary to remove the following line:
before invoking reconnect(), otherwise you'll run against a runtime error: it is a bug that I'm going to fix in our example
Thanks a lot ! I see the point : None has no close() method.
This line is also worthless before calling the bind() method ?
Similar Threads
-
By Alessandro in forum Client SDKs
Replies: 1
Last Post: December 18th, 2014, 05:15 PM
-
By keyan in forum Client SDKs
Replies: 4
Last Post: December 18th, 2014, 05:12 PM
-
By subuta in forum Client SDKs
Replies: 2
Last Post: January 5th, 2012, 08:53 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 08:09 AM.
Bookmarks