Subscription Request Handling
Submitted by Anonymous on Mon, 2007-03-19 19:27.
::
(I hope this is right place to discuss potential bugs in tigase server. If not, please let me know).
Consider this:
User A sends a subscription request to User B. Use B is online and receives the request. User B simply ignores the request and logs out. Later User B goes back online. At this point tigase includes User A in User's B roster with subscription status "none". Some clients do not display such roster items at all and some display it with some generic status.
It seems to me that the behavior ought to be to deliver the subscription request to User B on next login. This appears to be the behavior on jabber.org and with wildfire.
--Dmitry
Trackback URL for this post:
http://www.tigase.org/en/trackback/491
- Add new comment
- 1084 reads
Yes this is right place to discuss a potential bugs or even anything related to Tigase server.
What you are describing above is not a bug. It's a feature. I mean this behavior conforms XMPP RFC document: Integration of Roster Items and Presence Subscriptions. There is nothing in RFC which would suggest that server should push presence with subscribe every time user connects to the server.
I mean if the target user is off-line Tigase will deliver subscription request when user B login next time. But only once.
On the other hand however, behavior you described also does make sense.
I will contact EJabberd developers and Openfire developers to find out if their implementation follows any guidelines or Jabber extension. As behavior described by you is not a standard thing I would prefer to do it the same way as others to make it more compatible with the rest of Jabber world.
Please let me know if it didn't answer your question.