Opened 14 years ago

Closed 14 years ago

#12 closed enhancement (invalid)

PresenceClientProtocol should store current "state"?

Reported by: rcoup Owned by: ralphm
Priority: normal Milestone:
Component: generic Keywords: presence


For a persistent client app using presence, it seems like a good idea to maintain state across connections.

currently the pattern looks like:

presence = xmppim.PresenceClientProtocol()

But if the connection is lost and reconnected, then presence isn't re-announced.

So, PresenceClientProtocol could store the state set by the last call to available()/unavailable() and replay that when the connection is initialised. Or it could be a subclass PersistentPresenceClientProtocol if there are other usecases which don't want that behaviour.

See also #11

Change History (1)

comment:1 Changed 14 years ago by ralphm

  • Resolution set to invalid
  • Status changed from new to closed

Ah yes. The idea behind the protocol implementations in wokkel, like this protocol for presence, is that they don't have any business logic in them, but just the protocol.

What you suggest should probably be embedden in some generic client that among other things record presence. Also, the presence protocol itself might be enhanced upon by adding support for things like Entity Capabilities, in a derived class.

Closing this as invalid, but maybe there should be an other ticket for recording the desire for having such a generic client? Thanks for your input!

Note: See TracTickets for help on using tickets.