from dcrocker: > That is a dynamic requirement that depends upon the detail of the transport > and the receiver. > > That's the job of a protocol, not a format. from ned.freed: > A better approach would be to use BEEP's multiple > session capability -- the client could send the control document over and the > server could request things from the client on a different channel. The result > is a single connection, just in time data delivery, and no need for the client > to have to try and predict when the server will need something. from mtr: bingo! /mtrReceived on Tuesday, 17 April 2001 00:06:58 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 March 2006 20:11:28 GMT