[Bug 17795] Behavior of multiple connections to same node needs to be explicitly defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795

Robert O'Callahan (Mozilla) <roc@ocallahan.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |roc@ocallahan.org

--- Comment #1 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-19 05:07:19 UTC ---
This seems like an arbitrary limitation. It would be simpler for connect() to
always create a new connection than for connect() to sometimes not create a new
connection. What's the motivation for making the second connect() a no-op?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 19 July 2012 05:07:21 UTC