-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/20/12 9:39 AM, Mark Rejhon wrote: > Well -- As it stands now, reprogramming RealJabber to use > event=reset only (for both new and reset), or use event=new only > (for both new and reset), yields exactly identical behavior in > RealJabber. Absolutely no UI difference, when starting a new > message with event=reset, or refreshing a message in progress with > event=new. There is a legitimate question of confusion: Why have > both? > > Does this mean event=new should be merged with event=reset? I'd > just add a separate minor indicator (e.g. fourth attribute that is > purely optional) for those implementers that want to make a > distinction between new/reset in presentation purposes (e.g. green > flash or similar, for the start of a new message)
I think event='new' is probably fine for both. Clearly, somewhere along the line someone thought that the distinction was valuable (e.g., because a client might have expected a message with a <body/> at some point and never received it). That reminds me, is there value in describing the state machine a bit more completely? Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAyW/8ACgkQNL8k5A2w/vxW4gCeNRQh7JQibONlifYInstj3Vos pX4AoNlqQJHiYK0FMmXmYXgBqdhYqf6N =+bCd -----END PGP SIGNATURE-----
