W3C home > Mailing lists > Public > public-web-intents@w3.org > January 2012

[Bug 15726] New: Flesh out the Persistent connections section

From: <bugzilla@jessica.w3.org>
Date: Thu, 26 Jan 2012 07:14:43 +0000
To: public-web-intents@w3.org
Message-ID: <bug-15726-5094@http.www.w3.org/Bugs/Public/>

           Summary: Flesh out the Persistent connections section
           Product: Web Intents
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Intents specification
        AssignedTo: jhawkins@google.com
        ReportedBy: jhawkins@google.com
         QAContact: dave.null@w3.org
                CC: mike@w3.org, public-web-intents@w3.org,
                    paulkinlan@google.com, gbillock@google.com

>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?

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 26 January 2012 07:14:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:45 UTC