Hey guys,
Since the rfc3920 spec does not provide a clear description (i.e. example)
:) of how to relate TLS and server dialback I wanted to check with you my
interpretation. I'm trying to figure out the step where the server
dialback stream header should be sent from the Originating Server to
JDev,
Rod Chavez, an engineering manager with the Google Talk service will be
joining the jivesoftware.org weekly live chat next week:
When: Wednesday, September 28 at 9:00-10:00 AM PST (16:00 UTC/GMT)
Where: jivesoftware.org -- http://www.jivesoftware.org/group-chat.jsp
This will be a great
Hey all,
Sorry for two emails in a row... :) The other thing I wanted to announce
at jivesoftware.org is our newly launched Pampero Project -- an effort
to bring much greater scalability to Jive Messenger. You can read about
it at:
http://tinyurl.com/cqtg3
Our hope is that this effort can be
Justin,
Thanks for the ultra fast reply.
-- Gato
Justin Karneges [EMAIL PROTECTED] wrote in
message news:[EMAIL PROTECTED]
Hi,
Under RFC 3920, TLS is not possible with dialback. There have been some
efforts to go around this, but they are not in the spec.
-Justin
On Tuesday 20
Hi, I am a c++ programmer and never worked before with IM's I decided
for fun to start a client for myself.. there are already many out there
for me to start officially a new one.
I been reading some documentation, but it will really help a simple
strip down small client that I can read the
Maybe the two of you could discuss how and when S2S will be
implemented in your servers so that we can all join in from our
regular Jabber (or Google Talk) accounts. =P
Julian
On 21 Sep 2005, at 0:39, Matt Tucker wrote:
JDev,
Rod Chavez, an engineering manager with the Google Talk
Julian,
Maybe the two of you could discuss how and when S2S will be
implemented in your servers so that we can all join in from
our regular Jabber (or Google Talk) accounts. =P
We've supported s2s in Jive Messenger for almost two months (since the
2.2 release). However, we did just discover
