RE: [jdev] Re: Two questions regarding JEP-0124 HTTP Binding

can't the proxy figure out which port to use via DNS TXT records? Does the client really need to tell the proxy which port to use or is that task better left up to the proxy? Just asking. We went through this discussion in a long thread in June. Here is your concluding email:

[jdev] unwanted rate limiting in jabber1.4 w jadc2s and muc

Title: unwanted rate limiting in jabber1.4 w jadc2s and muc I'm working on an app where I need to send a high volume of messages from a user to a muc room (group of rooms really). It looks like something is limiting the rate of messages into rooms though. I can only seem to get one in every

Re: [jdev] Re: Two questions regarding JEP-0124 HTTP Binding

Ian Paterson wrote: can't the proxy figure out which port to use via DNS TXT records? Does the client really need to tell the proxy which port to use or is that task better left up to the proxy? Just asking. We went through this discussion in a long thread in June. Here is your concluding

[jdev] [ANN] Spark IM client

Hello all, We're pleased to announce the release of Spark 1.0, a free, cross-platform IM client. Windows and Mac releases are available now; a Linux version will be available in the near future. More information and downloads at: http://www.jivesoftware.org/spark/ Spark is optimized for use by

RE: [jdev] Re: Two questions regarding JEP-0124 HTTP Binding

Including the host and port still seems fine to me, I'm just not convinced it needs to be represented as an xmpp: URI. Why not just route=host:port? Well, URI's are for identifying entities that can communicate via XMPP. And the idea was that, a JEP-0124 proxy should also be able to support

Re: [jdev] Re: Two questions regarding JEP-0124 HTTP Binding

Ian Paterson wrote: Including the host and port still seems fine to me, I'm just not convinced it needs to be represented as an xmpp: URI. Why not just route=host:port? Well, URI's are for identifying entities that can communicate via XMPP. Well, xmpp: URIs are for use by non-native

RE: [jdev] Re: Two questions regarding JEP-0124 HTTP Binding

Hmm. So I could connect with my Jabber client to a JEP-0124 proxy that would enable me to authenticate directly with, say, an IRC server or SIMPLE server? The intention was only to enable *XML* protocols. For example, (future, proprietary) non-XMPP AJAX implementations that need to emulate

[jdev] [ANN] Other jivesoftware.org updates

Hello all, Sorry for two announcements in one day, but there's a lot happening at jivesoftware.org. :) Besides the launch of Spark, we also released: * Jive Messenger 2.3.0 (Open Source XMPP server) -- this release focuses on XMPP protocol compliance. TLS and SASL for c2s is now supported.