On Mon Mar 1 13:21:41 2010, chris wrote:
Anyway, my use case for this is generalized as such, and is not IM
related:
An internet connected client exists for [email protected], this
client
is the interface to many non internet enabled clients which are
identified by resources [email protected]/x1,x2..xn, where n could
be a
fairly large number. As x1..xn are all associated in a particular
way
for this use case, it makes sense (for reasons not here explained)
that
they are connected using a single bare JID, besides the fact that
maintaining many streams/connections is certainly not ideal and even
problematic.
But you're likely to be running your own extension anyway to talk to
these things, so you could make your XMPP client handle the routing
in other ways than try to break the 1:1 relationship between
connections and resources.
For instance, XEP-0030 encapsulates individually addressable objects
within a client perfectly well without introducing multiple resources
on a single connection.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
