Push Session Duration Too Short
Posted: 19 August 2009 10:20 AM   [ Ignore ]
Newbie
Rank
Total Posts:  2
Joined  2009-08-19

Session Duration for Push settings is too short (max is 1day), I don’t even load the app once a day.

BeejiveIM: 7days
IM+: 3days

I think there should even be an ‘indefinite period’ option, or at least a month.

Profile
 
 
Posted: 23 August 2009 10:29 AM   [ Ignore ]   [ # 1 ]
Administrator
Avatar
RankRankRankRank
Total Posts:  503
Joined  2006-11-12

Hello,

The policy depends on the XMPP server you are using. On OneTeam.im, the server does not allow to keep session for so long because it can be a security problem. Imagine you stay on for 7 days and join a heavy traffic groupchat: The server will have to buffer tens of thousands of messages. If you do that for many users, you could kill the server.

If you buy the module for ejabberd to deploy push on your own server, you can use whatever policy you want and if you want to risk killing your server or trust your users to do the right thing, this is up to you.

Profile
 
 
Posted: 25 August 2009 12:12 PM   [ Ignore ]   [ # 2 ]
Newbie
Rank
Total Posts:  2
Joined  2009-08-19

Thanks for the reponse,

That’s fair enough for group chat, but for ordinary chat isn’t there a way of allowing a limited buffer and unlimited timeout?

Out of interest, is there a limit to the extent of the timeout policy using ejabberd?

Profile
 
 
Posted: 25 August 2009 12:45 PM   [ Ignore ]   [ # 3 ]
Administrator
Avatar
RankRankRankRank
Total Posts:  503
Joined  2006-11-12

As I said this is a domain owner policy.
Of you run your own ejabber and buy the push module for Oneteam, you can define the policy you want and take the risk you want.

Note that you have the same security risk on the server with one to one chat. In 7 days you can receive a huge number of messages, legitimate or resulting from an attack.

So to summurize, run your own service and domain to solve your problem and use the policy you want.

Profile