[JDEV] File transfer and Jabber

Peter Sparago peter.sparago at snet.net
Mon Apr 23 19:08:08 CDT 2001


I thought I'd put my 2 cents in from the JAM perspective.

I am currently developing a commercial software product using Jabber as middleware for chat as well as information sharing. This product relies heavily on the "firewall friendly" single connection point messaging metaphor that Jabber has so elegantly implemented. As in the case of our app, not all uses of Jabber will be purely human to human messaging. 

To require the user to make additional connections or use other software in order to transfer non-chat information, in my opinion, would look like Jabber was only half a solution.  Corporate America has (reluctantly) bought into the messaging metaphor and sees it as safe and non-threatening. If the requirements are raised, many potential users, and software designers, will balk.

I agree with Jens that an in-band, priority based information transfer mechanism must be part of the protocol. Even if it is not implemented in high-performance chat only servers.
  ----- Original Message ----- 
  From: Jens Alfke 
  To: jdev at jabber.org 
  Sent: Monday, April 23, 2001 7:18 PM
  Subject: Re: [JDEV] File transfer and Jabber


  On Monday, April 23, 2001, at 02:40 PM, Todd Bradley wrote:


    Yes, but SMTP servers have never pretended to be
    "instant". If I'm running an INSTANT messaging
    server (which I am), I want the traffic to be as 
    lightweight as reasonable so that processing and
    delivery remains as INSTANT as possible.


  Well, I'm still waiting for evidence that file transfer is going to put excessive load on a Jabber server. But even so, the server could use simple quality-of-service techniques like lowering the priority of file-transfer IQ result elements to preserve the low latency of regular presence and messaging.

  —Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20010423/36a5dd66/attachment-0002.htm>


More information about the JDev mailing list