This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15726 - Flesh out the Persistent connections section
Summary: Flesh out the Persistent connections section
Status: NEW
Alias: None
Product: Web Intents
Classification: Unclassified
Component: Web Intents specification (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: James Hawkins
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 07:14 UTC by James Hawkins
Modified: 2012-07-24 17:44 UTC (History)
4 users (show)

See Also:

Attachments

Description James Hawkins 2012-01-26 07:14:42 UTC 
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?
Comment 1 Greg Billock 2012-07-24 17:44:18 UTC 
I've added this, but Respec isn't finding it in biblio.html. I've asked Robin how to repair this.