Re: [jdev] Second-guessing dns for s2s

2005-09-22 Thread Tijl Houtbeckers
On Thu, 22 Sep 2005 22:53:20 +0200, JD Conley <[EMAIL PROTECTED]> wrote: This is bad engineering i.t.o. creating undesirable impact on the broader Internet. What is the undesirable impact? Sure, there are a few more DNS lookups and potentially more connections and some stream errors. That

RE: [jdev] Second-guessing dns for s2s

2005-09-22 Thread JD Conley
> >>Interesting solution but not exactly standard, and will only > >>work between servers that are running Jive Messenger, > > > > True. However, the nice thing about the logic is that normal DNS is > > tried first. We also recommend that users setup DNS for max > > compatibility. Even so, the extr

[jdev] Second-guessing dns for s2s

2005-09-22 Thread Stephen Marquard
Matt Tucker wrote: Richard, Interesting solution but not exactly standard, and will only work between servers that are running Jive Messenger, True. However, the nice thing about the logic is that normal DNS is tried first. We also recommend that users setup DNS for max compatibility. Even so

[jdev] Webjabber 0.3.0 released

2005-09-22 Thread Zhong Li
Webjabber 0.3.0 released including Applet inside. Check out on http://www.webjabber.net Applet is fully plugin and configurable client side. We are still developing the configuration XML, please send your comments and requirements. You can easily add group chat and one-on-one chat(Live help) on you

RE: [jdev] [ANN] Google Talk engineering manager live chat

2005-09-22 Thread Matt Tucker
Richard, > Interesting solution but not exactly standard, and will only > work between servers that are running Jive Messenger, True. However, the nice thing about the logic is that normal DNS is tried first. We also recommend that users setup DNS for max compatibility. Even so, the extra logic

Re: [jdev] [ANN] Google Talk engineering manager live chat

2005-09-22 Thread Richard Dobson
Thanks for the bug report. We've now fixed the category and type (bug fix will be in next release). The name is now "Jive Messenger Server" by default, but that default can be changed by editing a configuration file. You are welcome ;) Yep, same issue -- http://www.jivesoftware.org/issues/brow