I'll be open sourcing this component pretty soon. The idea is that it
will have an adaptable storage system such that you can choose how you
are persisting your roster and presence info, but the API remains the
same. Though Anders and I have had many discussions about how it's
unfortunate that by choosing to create a component you MUST accept
responsibility for roster/presence. Ideally it would be nice in some
circumstances if you could re-delegate, or never accept responsibility
for those things from your jabber server if you wanted.
adam
On Jul 9, 2008, at 10:34 AM, Kevin Smith wrote:
On Wed, Jul 9, 2008 at 6:21 PM, Adam Pisoni <[EMAIL PROTECTED]> wrote:
I'm working on a component myself and have had to implement much of
the
roster stuff as well. I agree with Blaine that you can probably
implement
a fully featured/compliant PubSub within a component.
I'm impressed (and I think that's pretty cool, people have been saying
that you can't do the roster model, or the +notify stuff, from a
component, so I'm glad to see it done).
/K
