>> I think a <server_port/> subelement would be useful, because it would be >> clearer and more semantically correct than having a hostname:port string in >> the <server_address/> element (not to mention ipv6 addresses).
Yeah, it would mean that a client doesn't have to parse out the port from the rest of the host part. But that's really not that difficult, and is happening inside an XMPP client that is required to already know how to do that (of course, that may mean an underlying library ought to expose a helper method for it.. :) ). As for IPv6 addresses, you're supposed to enclose the IP address portion inside brackets [ ] to separate it from the port. > I would suggest you put that into <uri/> instead. Except that <uri /> looks to mean a URI for identifying/learning more about the game in question. Not where to connect to join the game. Mathieui: since it looks like you're the first to go this route in a while, let us know what you find experience-wise in practice. It could be worth revisiting 196 in-depth to mirror whatever information Steam provides for the equivalent feature in its client (especially if that data can be easily extracted). -- Lance
smime.p7s
Description: S/MIME cryptographic signature
