<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [JDEV] File transfers</TITLE>
<META http-equiv=Content-Type
content="text/html; charset=iso-8859-1"><DEFANGED_META
CONTENT="text/html; charset=us-ascii" HTTP-EQUIV="Content-Type"><DEFANGED_META
CONTENT="MS Exchange Server version 5.5.2653.12" NAME="Generator">
<META content="MSHTML 6.00.2716.2200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I fail to understand why providing a facility for
file transfers that can be enabled, disabled and limited server-side
is a problem. So, jabber.org won't run it. Fine. I'm sure lots of other jabber
servers administrators would like to provide file-transfer capability. If one
existed on the server, it could be communicated to the client. If a client is
trying to transfter to another client on a different server, then the servers
negotiate acceptable file-transfer parameters (the minimum of each server's
config for file size, timeout, etc), and communicate limitations back to the
client, including "server-assisted file transfer not supported," at which point
the clients could fall back to p2p.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I run a jabber server for my circle of friends. I
would turn on file service if it existed. I would probably limit it to a
specific list of userIDs and also limit bandwidth and transfers/hour. But I
would turn it on.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV></BODY></HTML>