> Mark Rotteveel wrote 06.01.2022 13:06:
> > BTW: I think in most cases you should be able to infer from the socket
> > error if the problem occurred on sending or on reading data (at least,
> > when using blocking socket reads/writes, not sure about non-blocking).
>
>It is not true:
>
>
>It is documented that successful return from function send() for TCP
> doesn't
> mean successful delivery of data to the target host, mere put them into
> socket
> buffer.
>If op_commit is sent but network error appear during waiting for
> response
> there can be two cases:
>1)
Mark Rotteveel wrote 06.01.2022 13:06:
BTW: I think in most cases you should be able to infer from the socket error if
the problem occurred on sending or on reading data (at least, when using
blocking socket reads/writes, not sure about non-blocking).
It is not true:
On 2022-01-05 21:48, Jiří Činčura wrote:
Yes. You probably have the same problem in your provider, no?
The problem exists there. Same as with fbclient. But I don't
explicitly solve it, application developer is responsible for handling
such scenario (if ever).
I agree. If the application
>Yes. You probably have the same problem in your provider, no?
The problem exists there. Same as with fbclient. But I don't explicitly solve
it, application developer is responsible for handling such scenario (if ever).
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel
Em qua., 5 de jan. de 2022 17:14, Dimitry Sibiryakov
escreveu:
> Jiří Činčura wrote 05.01.2022 19:44:
> > You're probably thinking about something in client library?
>
>Yes. You probably have the same problem in your provider, no?
If no response or network error is returned, application
Jiří Činčura wrote 05.01.2022 19:44:
You're probably thinking about something in client library?
Yes. You probably have the same problem in your provider, no?
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
05.01.2022 15:03, Dimitry Sibiryakov wrote:
Hello All.
It is documented that successful return from function send() for TCP doesn't mean successful delivery of data to the target host,
mere put them into socket buffer.
If op_commit is sent but network error appear during waiting for
One way to handle this is via manual inserts (and deletes) in a dedicated
table. Something like:
1. Insert a row into the table at the beginning of each transaction.
2. If the connection fails during the commit, check for the presence of the
corresponding row in the database.
- If the row is
Hello All.
It is documented that successful return from function send() for TCP doesn't
mean successful delivery of data to the target host, mere put them into socket
buffer.
If op_commit is sent but network error appear during waiting for response
there can be two cases:
1)
Hello All.
It is documented that successful return from function send() for TCP doesn't
mean successful delivery of data to the target host, mere put them into socket
buffer.
If op_commit is sent but network error appear during waiting for response
there can be two cases:
1)
11 matches
Mail list logo
