Currently there is no support for this. I didn't encounter a need for it, so I didn't bother adding it. Currently, the only way to send a datagram is via the Comm::send_datagram API which doesn't accept a dispatch handler as one of its arguments. However, it would be fairly easy to add. You could add a dispatch_handler argument to Comm::send_datagram() that defaults to 0. Inside the method, if the dispatch_handler is set, then it can register the request in the pending request queue.
- Doug On Fri, Jan 23, 2009 at 4:36 PM, Mateusz Berezecki <[email protected]>wrote: > > Hi list, > > I'm trying to figure out from the documentation (not really feeling > like digging that deeper today) if a DispatchHandlerSynchronizer can > be used for datagram tranmissions? The use case being datagram request > arriving at one server, and the function not returning before that > server returns with the response datagram. > > The documentation says: > "This class is a DispatchHandler class that can be used by a client to > synchronize with response messages resulting from previously sent > request messages." > > Does the "sent request messages" imply the usage of send_request() API > ? Is there already any way to perform synchronized UDP communication > using current Hypertable code base ? > > Mateusz > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en -~----------~----~----~----~------~----~------~--~---
