-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 7 Jan 2004 00:06, [EMAIL PROTECTED] wrote:
> A solution would be to modify the server to store *any* message for a user X
> until something gets received from the c2s connection of user X or he logs
> off. This should implement at-least-once semantics in contrary to
> at-most-once semantics at the moment.
With luck a change like this might only require changing the offline message
module. It does somewhat break the semantics of offline messages a little,
instead of getting no message you might potentially get many copies of the
same message. Usually harmless, but amusing if the message contained the
body, "What?" or something similar. :-)
If message events (client confirming receipt) ever become widespread, _that_
would be a better way to go about it. At the very least you can detect if a
resource supports them as soon as it sends a message, and use that
information to provide more reliable transport.
Anyone up for the task? ;-)
TX
- --
'Every sufficiently advanced technology is indistinguishable from magic' -
Arthur C Clarke
'Every sufficiently advanced magic is indistinguishable from technology' - Tom
Graves
Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
Web site: http://xaoza.net/trejkaz/
Jabber ID: [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/+rdzmifzwBMPxxoRArTMAJ9bKNDfiW87cbWh0eiT4wcADil/wgCdFbzv
/193ycjkqC/PHQyrv91KOUQ=
=K4o6
-----END PGP SIGNATURE-----
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
