<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=windows-1252"> <META content="MSHTML 5.50.4611.1300" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial>I thought I'd put my 2 cents in from the JAM perspective.</FONT></DIV> <DIV><FONT face=Arial></FONT> </DIV> <DIV><FONT face=Arial>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. </FONT></DIV> <DIV><FONT face=Arial></FONT> </DIV> <DIV><FONT face=Arial>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.</FONT></DIV> <DIV><FONT face=Arial></FONT> </DIV> <DIV><FONT face=Arial>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.</FONT></DIV> <BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV> <DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> <A title=jens@mac.com href="mailto:jens@mac.com">Jens Alfke</A> </DIV> <DIV style="FONT: 10pt arial"><B>To:</B> <A title=jdev@jabber.org href="mailto:jdev@jabber.org">jdev@jabber.org</A> </DIV> <DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, April 23, 2001 7:18 PM</DIV> <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [JDEV] File transfer and Jabber</DIV> <DIV><BR></DIV>On Monday, April 23, 2001, at 02:40 PM, Todd Bradley wrote:<BR><BR> <BLOCKQUOTE>Yes, but SMTP servers have never pretended to be<BR>"instant". If I'm running an INSTANT messaging<BR>server (which I am), I want the traffic to be as <BR>lightweight as reasonable so that processing and<BR>delivery remains as INSTANT as possible.<BR></BLOCKQUOTE><BR>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.<?color><?param 0000,0000,DEB7><BR><?/color><BR><?fontfamily><?param Marker Felt><?color><?param 0000,5151,0101><?bigger><?bigger><?bigger><?bigger>—Jens<?/bigger><?/bigger><?/bigger><?/bigger><?/color><?/fontfamily></BLOCKQUOTE></BODY></HTML>