One other option is to only allow one connection by IP, but this could lead to some issue (as there could be more than one real user with one IP). Pat wrote: > That sounds great. One drawback I see if it being on the server side > versus client side is that if someone creates multiple accounts > (separate logins) they would still be able to open multiple windows > and essentially battle themselves and advanced the main account by > using the other as simply a stepping stone. > > This is probably a more complex issue then when I first thought > because they could also open multiple windows via different browsers > but at least with your suggested C module they would not be able to > login to the same account. > > On Aug 6, 7:07 am, Nicolas Trani <[email protected]> wrote: > >> Hi, >> >> Yes you can limit APE instance, but you have to write a C server side >> module. Just create a module (or modify the chat module) and make it >> identify user with a login/password when a new user connect check that >> there is no other user are already connected with the same user/password. >> This is the most secure way to limit user to one single instance. There is >> some other way to do this on the client side (but as it is on the client >> side this can be easily "hacked"). There is some documentation on the wiki >> on how to write server module. >> >> For now it's only possible by writing a module in C but in a near futur >> this will be possible with javascript on the server side (we are currently >> working on it) >> >> Regards. >> >> On Wed, 5 Aug 2009 21:54:16 -0700 (PDT), Pat <[email protected]> >> wrote: >> >> >> >> >> >> >>> Hello! >>> >>> First off I am stoked to have found APE. Although I dont have a need >>> for it this instant I can see many cases where this will be an >>> absolute must. I have a few projects in the pipeline that I cannot >>> wait to explore further. >>> >>> I noticed that ape uses 0.ape 1.ape etc to bypass the connection >>> limits. However is there any code that would limit a user to just one >>> instance. For example a real time... shooter game. Having multiple >>> windows open both loading the same thing and having both windows >>> updated I believe would be a strain on the users computer. Is it >>> possible to allow only a single instance running and if another >>> instance is detected to alert that user that it is already open and >>> close the window. >>> >>> In ajax I would probably do this by setting an ID in the session or >>> passing it through and checking that ID upon the ajax call so if they >>> load a new window the ID would change and the old window would simply >>> display and alert and shut down the requests. >>> >>> Im not quite sure how this would be accomplished with APE since it >>> pushes the data. Does anyone have any ideas? >>> >>> Im now a twitter and google group follower and I cannot wait to see >>> what is in store for this project! >>> -- >>> >> Nicolas Trani - Développeur web >> Weelya - Improve the web >> Tel : 06 24 46 88 27 >> > > >
-- Nicolas Trani Weelya - Improve the web http://www.weelya.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/ -~----------~----~----~----~------~----~------~--~---
