Re: [jdev] deferred delivery
Tijl Houtbeckers wrote: It's possible to use XMPP in a store and forward fashion, you wouldn't need to modify the protocol for it. It's still an edge case though. A good reason for XMPP to replace email in my opinion is this concept of instant error reporting. Yes. The idea of instant error is interesting, but the problem for what to do with the error then rely on the client. If this is a simple chat message, then no problem, I wait for the next time I see my correpondant online. But if this is an important message that I want him to read as soon as he gets online ? I am using Jabber as some kind of text voicemail for people that are not reachable. I agree however that I never encountered a Jabber server that was down when I tried to leave a message waiting for someone. And I agree that the problem with mail is to process error message that come afterwards. Clients has still to process the error message when it comes as a definitive failure of delivery. -- Mickaël Rémond http://www.erlang-projects.org/ ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] deferred delivery
On Tue, 01 Mar 2005 11:26:33 +0100, Mickael Remond [EMAIL PROTECTED] wrote: Tijl Houtbeckers wrote: It's possible to use XMPP in a store and forward fashion, you wouldn't need to modify the protocol for it. It's still an edge case though. A good reason for XMPP to replace email in my opinion is this concept of instant error reporting. Yes. The idea of instant error is interesting, but the problem for what to do with the error then rely on the client. If this is a simple chat message, then no problem, I wait for the next time I see my correpondant online. But if this is an important message that I want him to read as soon as he gets online ? I am using Jabber as some kind of text voicemail for people that are not reachable. I agree however that I never encountered a Jabber server that was down when I tried to leave a message waiting for someone. And I agree that the problem with mail is to process error message that come afterwards. Clients has still to process the error message when it comes as a definitive failure of delivery. You can do two things.. modify an existing server to use store-and-forward, perhaps only under certain conditions (take a look at AMP, http://www.jabber.org/jeps/jep-0079.html ). Or you could write a component that delivers a message (if it's located on your own server, it could even spoof the from JID in most cases, take a look at the recent thread about that). The latter idea would be more for when the user expclitly wants to use it to leave a message (I can imagine a client could try to deliver it the normal way, and when it gets an error offer to deliver it using that service). The advantage is it would (potentially) work on all jabber servers that support components, and people from other server could use it too (if you allow that, and without the spoofing ofcourse). ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] deferred delivery
Tijl Houtbeckers wrote: You can do two things.. modify an existing server to use store-and-forward, perhaps only under certain conditions (take a look at AMP, http://www.jabber.org/jeps/jep-0079.html ). Or you could write a component that delivers a message (if it's located on your own server, it could even spoof the from JID in most cases, take a look at the recent thread about that). The latter idea would be more for when the user expclitly wants to use it to leave a message (I can imagine a client could try to deliver it the normal way, and when it gets an error offer to deliver it using that service). The advantage is it would (potentially) work on all jabber servers that support components, and people from other server could use it too (if you allow that, and without the spoofing ofcourse). You proposal seems consistent to me and is a better way that trying to mask the error. Having an explicit service that will try to resend the message on your behalf is clean and consistent with Jabber. Thank you ! -- Mickaël Rémond http://www.erlang-projects.org/ ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
[jdev] messagebody limit's?
Hello everyone! I try the tipic JABBER server and I cant send large messages to a group. Are there limits on size in XMPP? My messages are up to 800 kB utf. The Client works inside the application. Do the jabber 1.4 or 2 route such messages? Thanks Uwe ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
[jdev] Heartbeat and tcp keepalive
Developers, I'm integrating test equipment and GUIs using XMPP, works great. Well except for when my test equipment-XMPP single board computer is switched off. The server doesn't recognize that the SBC is offline for quite some time (same problem as the disconnected dialup laptop user in a chat scenario) because of the Linux timeout settings in proc/sys/net/ipv4/. I found this thread http://mail.jabber.org/pipermail/jadmin/2004-April/015513.html but there wasn't a mention of specific settings to reduce the timeout. I'm wondering if someone out there has tweaked their TCP timeout settings combined with jabberd 1.4.3's heartbeat to recognize the disconnected client in under 60 seconds. I'd actually like 5 second discovery, heartbeat traffic is not a concern because all my equipment is connected to the same 100Mb/s switch. If you've successfully configured your system to reduce the timeout, can you forward your proc/sys/net/ipv4/ settings? Thanks, Craig -- Dr. Craig Hollabaugh, [EMAIL PROTECTED], 970 325 0509 Author of Embedded Linux: Hardware, Software and Interfacing www.embeddedlinuxinterfacing.com ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
[jdev] Re: messagebody limit's?
Uwe Herrmann wrote: Hello everyone! I try the tipic JABBER server and I cant send large messages to a group. Are there limits on size in XMPP? My messages are up to 800 kB utf. The Client works inside the application. Do the jabber 1.4 or 2 route such messages? jabberd2 doesn't have any specific limits on message size. Depending on the backend database and database schema in use, there can be limits on the size of messages stored in the offline queue. Regards Stephen ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] Jabberd2 for Windows?
As long as you don't need anything specific to jabberd2 there are several other options, especially for windows. If you want to stick with open source, check out Jive Messenger http://www.jivesoftware.org. There is a non-expiring limited user demo version of Coversant Soapbox server http://www.coversant.com which would give you a free (but not open source) setup and is tightly integrated into windows - probably a good fit for local client development testing. -iain On Mar 1, 2005, at 12:35 PM, Anthony Ortiz wrote: Hello everyone, I'm looking to test some client code against a jabberd2 server but can't find an implementation in Windows. I'm curently running jabberd 1.4.2 on my local machine but it doesn't support the latest and greatest protocols. I guess I may have to resort to testing against someone else's jabberd2 server, but it sure would be nice to have it running locally in debug mode so that I can see all the messages going back and forth. Anyone? Thanks! Anthony ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
RE: [jdev] Jabberd2 for Windows?
As long as you don't need anything specific to jabberd2 there are several other options, especially for windows. If you want to stick with open source, check out Jive Messenger http://www.jivesoftware.org. There is a non-expiring limited user demo version of Coversant Soapbox server http://www.coversant.com which would give you a free (but not open source) setup and is tightly integrated into windows - probably a good fit for local client development testing. Actually it's www.coversant.net. JD Conley ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] Jabberd2 for Windows?
better use ejabberd On 1 Mar 2005 at 15:35, Anthony Ortiz wrote: Hello everyone, I'm looking to test some client code against a jabberd2 server but can't find an implementation in Windows. I'm curently running jabberd 1.4.2 on my local machine but it doesn't support the latest and greatest protocols. I guess I may have to resort to testing against someone else's jabberd2 server, but it sure would be nice to have it running locally in debug mode so that I can see all the messages going back and forth. Anyone? Thanks! Anthony ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] Heartbeat and tcp keepalive
To get to a 5 second timeout, you will need to heavily modify not just the keepalives, but put your stack in a non-standard tcp timeout mode (default timeouts on linux take nearly 4 minutes). These settings I believe are all operating-system wide. On Tue, 01 Mar 2005 12:19:34 -0700, Craig Hollabaugh [EMAIL PROTECTED] wrote: Developers, I'm integrating test equipment and GUIs using XMPP, works great. Well except for when my test equipment-XMPP single board computer is switched off. The server doesn't recognize that the SBC is offline for quite some time (same problem as the disconnected dialup laptop user in a chat scenario) because of the Linux timeout settings in proc/sys/net/ipv4/. I found this thread http://mail.jabber.org/pipermail/jadmin/2004-April/015513.html but there wasn't a mention of specific settings to reduce the timeout. I'm wondering if someone out there has tweaked their TCP timeout settings combined with jabberd 1.4.3's heartbeat to recognize the disconnected client in under 60 seconds. I'd actually like 5 second discovery, heartbeat traffic is not a concern because all my equipment is connected to the same 100Mb/s switch. If you've successfully configured your system to reduce the timeout, can you forward your proc/sys/net/ipv4/ settings? Thanks, Craig -- Dr. Craig Hollabaugh, [EMAIL PROTECTED], 970 325 0509 Author of Embedded Linux: Hardware, Software and Interfacing www.embeddedlinuxinterfacing.com ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
Re: [jdev] Heartbeat and tcp keepalive
On Tue, 2005-03-01 at 17:46 -0700, David Waite wrote: To get to a 5 second timeout, you will need to heavily modify not just the keepalives, but put your stack in a non-standard tcp timeout mode (default timeouts on linux take nearly 4 minutes). These settings I believe are all operating-system wide. David, Where did you arrive at 4 minutes? All my debian machines have /proc/sys/net/ipv4/tcp_keepalive_time at 7200 which is 2 hours. Thanks, Craig ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
[jdev] PyICQ-t, PyAIM-t, and JWGC moved to new site
Folk, All of my projects are now hosted in a single central location, http://www.blathersource.org/. Each project's repository is now under Subversion (svn.blathersource.org) instead of CVS. All of my mailing lists (py-transports, jwgc) are now hosted at blathersource.org. Each project's respective home pages are now: - PyICQ-t: http://pyicq-t.blathersource.org/ - PyAIM-t: http://pyaim-t.blathersource.org/ - JWGC: http://jwgc.blathersource.org/ I will transfer bug reports and the like over from JabberStudio when it is back to life and/or I can get access to my data from the database in some way. Likewise, I will have them converted to off-site projects. The new site is functional, but is not complete. I have a lot of other features I am working on adding/improving, but I decided it is functional enough at this point to post. And before anyone asks, there are no current plans for other projects at the site other than my own. ;) I simply wanted a good central place to put my things. Note: This change does not affect scriptrepo, which I have been maintaining for a little bit now. It will always live on jabberstudio. I may set up a read-only mirror for it at blathersource at some point but I am not yet sure about that. Many thanks to Modevia.com for providing wonderful hosting services! Daniel -- The most addictive drug in the world is music. - The Lost Boyz ___ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
