15726 2012-01-26 07:14:42 +0000 Flesh out the Persistent connections section 2012-07-24 17:44:18 +0000 1 1 1 Unclassified Web Intents Web Intents specification unspecified PC All NEW P2 normal --- 1 jhawkins jhawkins gbillock mike paulkinlan public-web-intents dave.null oldest_to_newest 63145 0 jhawkins 2012-01-26 07:14:42 +0000 From http://lists.w3.org/Archives/Public/public-web-intents/2012Jan/0015.html Section 5.3, Persistent connections: "A third is returning a MessagePort to the client which can be used for subsequent communication." . This wording implies that the service returns the MessagePort that is returned as result data. However, according to mail discussions it seems as the preferred solution is that the Client allocates the MessagePort that is sent as payload data to the Service. It would also be good to elaborate more and include examples on all the methods for achieving persistent connections. Should this be part of a normative section or stay informative? 71413 1 gbillock 2012-07-24 17:44:18 +0000 I've added this, but Respec isn't finding it in biblio.html. I've asked Robin how to repair this.