[jdev] Jabber message Maximum length
Michal vorner Vaner
michal.vaner at kdemail.net
Wed Aug 23 09:15:13 CDT 2006
On Wed, Aug 23, 2006 at 12:28:44AM +0300, Joonas Govenius wrote:
> >About sending the image, I would recommend using something like stream
> >initiation (jep-0095), since you can open outbound stream which is much
> >less data consuming, and use inbound only when necessary.
> Stream Initiation provides a way to negotiatie streams "between any
> two entities". That leaves two options for a multiuser case:
> 1. The sender negotiates a stream with each of the other participants
> in the sessions and sends the image to each seperately.
And you do not send the messages with data to all of them? I know, there
is multicast component, but it is not much used in the wild. I did not
met a server that had said component.
> 2. Serverside support: the sender negotiates a stream with the server
> and the server negotiates a stream with each of the other
> Option 1 doesn't seem feasible and option 2, well, requires serverside
> Additionally, a central idea in the whiteboard protocol I'm using is
> that each participant has an equivalent copy of the whiteboard's
> contents. That would break if the stream negotiation fails with one of
> the participants.
> >Because, if
> >you send that 200kB image, you will probably exceed not only the message
> >size (which you can solve by splitting it), but as well will get a karma
> >limit and you will be blocked for a while before the rest will be sent
> >out. Transfer of such image will take several seconds on most servers
> >out there. For example, default setup of ejabberd allows something like
> >7kB/s for a single user.
> That's too bad, but if the messages do eventually get delivered, it's
> tolerable. I haven't figured out better way to do it without
> serverside support.
Hm, you could send something like "Place a picture here, it will be this
large and I will send it out of bound" using jabber and then transfer
the image itself somehow outside, like the SI, or, we have jingle
already, right? Google talk uses it to file transfers, so it could be
used somehow for these images as well (they said they will have some
example of tcp-like over jingle in next version of libjingle).
The client would draw something like an empty frame before the image is
available to show there is something, like a web browser.
> Like Peter said, it would be interesting if server developers could
> propose some recommended sizes.
One semi-random fortune:
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary. No such faith comforts the software
-- Fred Brooks
Michal "vorner" Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the JDev