RE: [JDEV] Large Jabber Messages

["Thomas Charron" <tcharron@nermail.ups.com>]

	I disagree about the obviouse solution..  The obviouse solution would be to
split the large amount of data into smaller packets that can be reassembled
at the client end..

	In your solution, the messages will still pile up, but in an IP way instead
of a Jabber packet way.  This is simular to what I've done to allow file
transfers by uuencoding, splitting up, and transfering it via multiple
packets..

	(The source I'm using isn't out there quite yet, hopefully sometime late
this week/next weekend..  I want a decent looking Win32 client for 0.6
release)

--
Thomas Charron
United Parcel Service
Northeast Region
"Moving at the speed of a T3 Trunk Line!"


> -----Original Message-----
> From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of
> qbradley@csc.UVic.CA
> Sent: Monday, April 12, 1999 1:28 PM
> To: jdev@jabber.org
> Subject: [JDEV] Large Jabber Messages
>
>
>
> I was thinking about sending "Voice" messages in Jabber, which are Jabber
> packets that contain a wave form to be played.  They could be quite large.
> If it was large enough, and the clients connection was slow enough, other
> messages would pile up behind it while it transferred.  This is a natural
> consequence of having only one Socket.
>
> The obvious solution is to use two sockets, one for "bulk" traffic over a
> certain size, and another for small messages.
>
> Happily, there already seems to be a provision for such in Jabber.
> Clients can log in multiple times as the same user but with different
> "nicks".
>
> It seems that what hasn't been discussed is some kind of attributes, or
> perhaps "hints" for the server, along the lines of "forward messages of
> size X or larger to this other nick instead".
>
> Just a thought
>
> Quetzalcoatl Bradley
> qbradley@csc.uvic.ca
>