[ticker-dev] Ticker group "invitation" attachments
Phillips, Matthew
Matthew.Phillips at dsto.defence.gov.au
Tue Aug 24 23:10:45 CDT 2004
[David]
> Matthew> Ticker-Group: 1.0
>
> Is this value a string? Or a float?
>
> We ended up using an int32 (major * 1000 + minor) for Chat messages?
>
> We also used "org.tickertape.message" to identify the
> protocol -- should this be "org.tickertape.group" for consistency?
>
> Matthew> Name: Private Chat
> Matthew> Type: chat
>
> Ok.
>
> Matthew> Private-Keys: Private Chat,My Private Key
>
> Is there some reason you'd prefer commas instead of
> vertical-bars as used for the other lists of strings in the
> Tickertape and Presence protocols?
I probably should have made it clearer that I intend this as the payload of a MIME attachment rather than as a notification format. So the "tricks" we've used for version numbers and lists to make it possible to intelligently subscribe to notifications in that format have given way to what (I think) are more human-friendly.
> How does this work -- if you sent me this message, where would I get
> the key values from? If I already had them, isn't it likely that
> mine would have different names to yours? (ie. "My Private
> Key" would be a fine key name, but not so good when sent to
> someone else)
Yes, I agree this could be seen as slightly bogus. However, I basically intend this to be used in the scenario where I'm setting up a new secure group and email the key around (or whatever) and then send out an invitation on ticker (in the case where we already have an appropriate key, the first step can be skipped). Short of embedding the actual key in the invite, which would be pointless unless we already have a secure group to use, the use of key names is the only way I can think of (I'm assuming that using unique key names is the best way to manage otherwise anonymous chunks of data). If you don't have the key(s), then you should get warning: no biggie, you just need to do it manually.
[David]
> Matthew> Just out of interest: am I the only one doing, or planning
> Matthew> to do, any serious development in the ticker/presence area?
>
> Did you see Ted's recent release of xtickertape-2.0rc1 ?
I did, but I assumed this was a fairly minor bug-fix release? Not sure why I assumed that, except that I get the impression Ted's not doing much active development of xtickertape right now.
Matthew.
More information about the ticker-dev
mailing list