|
|
|
|||||
|
can tcp oneway failure go unnoticted?
I see in the documentation that oneway invocations only wait on the local tcp/ip stack and do not return socket failures. My question is: can a tcp oneway invocation on a proxy fail due to a SyscallException (or derived), but the proxy recovers, and proceeds without problem. My situation is that I want to be able to make non-blocking reliable invocations. Its ok to lose an invocation, but only if I know no subsequent reliable invocations will succeed. Is tcp oneway safe for this use or should I stick with two-way?
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| assertion failure | bravekillla | Help Center | 1 | 12-27-2005 05:34 PM |
| Delay of OneWay-Calls | wgwolf | Help Center | 1 | 11-10-2005 09:24 PM |
| Pre-Build Failure | Wayetender | Help Center | 8 | 08-07-2004 08:06 PM |
| OneWay Method invokation NOT returning | galbe | Bug Reports | 7 | 10-30-2003 10:07 AM |
| Making C++ throughput demo oneway? | SteveWampler | Help Center | 4 | 09-02-2003 06:14 PM |