[JDEV] Feature negotation/File transfers..

[Seth Hartbecke]

Please remember that whatever we use for CTCP/MIME/(name or favorite
feature) needs to be easily done/undone by the transports.

The major selling point of jabber is NOT that it uses XML/MIME/CTCP or
CTSP. You average user is not going to care (programmers trying to write a
client will).

What they will like about jabber is how they can talk with anybody on
ICQ/AIM/IRC/Yahoo/(Name your 2nd favorite IM here) without having to
run multiple clients.  This is the market I think we should be
targeting.  I am just concerned that the stuff we are talking about will
not "transport" invisialy to these other environments.

On Mon, 9 Aug 1999, Patrick McCuller wrote:

> 
> 
> > -----Original Message-----
> > From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> > Thomas D. Charron
> >
> >   To start, this is a REALLY good post..  Albeit a bit long..
> >
> 	Please forgive me. The more frustrated I get, the more I write... :)
> 
> 
> > >Client A: Hi, I want to send you a binary file.
> > >Client B: OK, how about HTTP?
> > >Client A: Alright. Pick up the file at
> > >http://102.102.102.102.102.102.102:45000/file_6_6_4.tgz
> >
> >   Almost EXACTLY the example used several months ago..
> >
> 	That was my intention (I didn't check the originals, though, perhaps I
> should have). I hope no one's gotten the impression that I'm touting this as
> my idea or anything. It isn't. It does feel right.
> 
> 
> > >Client A: I want to send you a JPG image.
> > >Client B: Don't. I am a toaster.
> >
> > *ROTFL*
> 
> 	I know it isn't cool to laugh at your own jokes, but this one got me too.
> :>
> 
> >
> >   Yet another feature negotiation example..  Same would be:
> >
> > Client A: I want to send you a file.  I prefer MIME encoding via
> > Jabber stream.
> > Client B: Unsupported in this client.  I prefer HTTP download..
> > Client A: Unsupported in this client.  My secondary preference is
> > UUENCODE Jabber stream.
> > Client B: Can do, here comes, conversation ID: 17826482
> >
> >   This case would assume it was a file transfer, and not some
> > stream or anything..
> 
> 	This is a great example.
> 
> 	Naturally, clients should avoid sending large things through the jabber
> network - for lots of reasons. Possibly one of the most important being that
> servers are likely to put an upper limit on the length of messages they will
> accept.  :)
> 
> 
> Patrick
> 
> > ---
> > Thomas Charron
> >
> >
> >
> >
> > --== Sent via Deja.com http://www.deja.com/ ==--
> > Share what you know. Learn what you don't.
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> >
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>