On 27 трав. 2010, at 12:45, Viktor Klimov wrote:
> You mean a packet message used in the TCP? Or offer to implement ACK to PB?
>
The latter one. An application-level ack. You only accept a transaction when
you have „acked” to your peer that you have the full data payload, and after it
acks yo
You mean a packet message used in the TCP? Or offer to implement ACK to PB?
Maybe someone will point to the literature on network programming in
unstable networks?
On Tue, May 25, 2010 at 6:41 PM, Yaroslav Fedevych
wrote:
> In your case, I would suggest that the server sends some sort of ACK
> a
In your case, I would suggest that the server sends some sort of ACK
after it has received the payload from client, and the client must
send the same kind of ACK in response. Only after that would the
server consider operation complete, otherwise it would either inform
the client that the previous
Hi Glyph, sorry for my english.
My server.py save last answer(see User.perspectiveMessageReceived).
Client when an error occurs(in callRemote) schedule reconnect. After
reconnect client call remote method which return last answer.
It works if disconnect happened when server send data to
client(_
On May 23, 2010, at 11:54 AM, Viktor Klimov wrote:
> I use PB in unstable network. The server remembers the last answer.
> Client detection disconnected, connected again, makes entry into the
> system and calls the function returns the last response
> (get_last_response). The answer, it returns a
I use PB in unstable network. The server remembers the last answer.
Client detection disconnected, connected again, makes entry into the
system and calls the function returns the last response
(get_last_response). The answer, it returns a deferred saved earlier.
If somewhere an error cycle repeats.
