> > I'd much rather add a query to the URL indicating the action:
> >
> > jabber:[EMAIL PROTECTED]?action=message # send IM (default action)
> > jabber:[EMAIL PROTECTED]?action=roster # add to roster
> >
> > jabber:[EMAIL PROTECTED]?action=chat # join a chat room
>
> I think this makes a lot of sense, as it doesn't muddy the
> JID part of the URL and is a clean and flexible way of doing
> things. And it's also a format we're familiar with (HTTP GET URLs).
>
> Ironically, I guess the achilles heel is the flexibility:
>
> jabber:[EMAIL PROTECTED]?action=chat # join a chat room
>
> vs
>
> jabber:[EMAIL PROTECTED]?action=join # join a chat room
jabber:[EMAIL PROTECTED]?action=chat joining a chatroom could get
confusing. I would have assumed it would have started a line-by-line
private chat (as opposed to sending a "normal" message- see
http://docs.jabber.org/jpg/html/main.html#REFMESSAGE for details).
Having two "chat" types in Jabber does confuse things a little...
Michael.
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
