On Jul 30, 2008, at 8:40 PM, Peter Saint-Andre wrote:
Dave Cridland wrote:
On Wed Jul 30 13:55:56 2008, Pedro Melo wrote:
The most important part of -1 resources are their caps. For
example, I can have a calendar app logged in with my own jid,
accepting some namespace for calendar updates or meeting requests.
Are you suggesting a sort of negative disco feature which indicates
that the XMPP entity is not an IM resource at all? Could this be
done with a suitable category/type? Moving forward, this would
allow clever clients to observe that it wasn't a IM client capable
of handling calendaring requests, but a dumb calendaring bot
working on behalf of the user.
If you're not suggesting this, can I suggest it? :-)
I think he's suggesting that the disco identity of your calendar
would be something like this:
<identity category='automation' type='calendar'/>
Exactly.
But you would need to complement this with <features> to specify the
protocol that the agent uses to receive calendar requests/updates.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
