I had a similar use case and I ended up using MUC, it is also a pubsub model with the advantage of having presence built-in.
-- Camilo Aguilar Software Engineer On Wednesday, November 28, 2012 at 9:06 AM, Kevin Smith wrote: > On Wed, Nov 28, 2012 at 2:04 PM, andy nes <[email protected] > (mailto:[email protected])> wrote: > > Assuming Presence based on whether or not geolocation data is published, > > might not work in my case. The publisher has more than one status in > > available mode and the subscriber should know what status the Publisher is > > in. The Publisher can be dnd, idle, away etc. Depending on the Publisher's > > status, the handling of geolocation data varies. > > > > So, any suggestions on how to achieve this? > > What you're describing is pretty much exactly the roster/presence/PEP > model. You can rebuild this without using the roster but you'd > essentially be reinventing the roste, presence and PEP technologies. > Why not use them as-is? > > /K
