GCN-XML and Dakota

[Alasdair Allan]

> -- Each uses the uncommon idea that the receiver of the message initiates the connection (usually the sender connects).

The vTCP paradigm is that the received makes a client connection to the broker's server. Messages are pushed by the broker down these connection. I'm not entirely sure where you get the idea that this isn't the case?

3.2    Broker to Subscriber
When a subscriber wants to receive VOEvent message traffic, it opens a TCP connection to a broker. This connection is kept open continuously. When the broker receives a message, it relays a copy of the VOEvent message to all of the connected subscribers. Thus, a subscriber must continuously listen on the TCP connection and be prepared to receive VOEvent messages at any time, even when it is busy processing a previously received VOEvent message. When a subscriber receives a VOEvent message from its broker, it sends back a response. The response from the subscriber is a Transport message.


This isn't "uncommon" that's how the majority of network protocols work, a client makes a connection to a server which it wants to get information from. That's how the WWW works after all? 

Al.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20120125/6c54d35d/attachment.html>