|Re: [ecf-dev] iPOPO Compatible Providers|
On 11/20/2013 01:52 AM, Thomas Calmant wrote:What about re-using an existing multicast-based solution like pyzeroconf
> I got a case where services had serveral, very long properties values
> (full text strings), which implied to send packets larger than 1600
> bytes on notifications (registration and update).
> Of course, it raised the UDP packet ordering problem, so I decided to
> use multicast for small event packets only, and HTTP for information
> This is one implementation of a discovery protocol: other
> implementations can ignore the dispatcher servlet.
> Also, in this case, the HTTP server must be active for JSON-RPC to work,
> so there were no real constraint against this servlet.
> New providers can work without the dispatcher servlet without problem,
> as long as we have this "horror case" (the problematic exported service
> has been cleaned up since).