I also want to know if one channel per user is a scalable plan... On Jul 24, 3:12 pm, maku <[email protected]> wrote: > Hi, > > I would like to develop the following use case: > > when a client session starts - the client connects to APE with an > unique ID. > > Further an application server (java) has events which should be > delivered to the client. So the idea is that the application server > calls the APE server with a http request and the unique id of the user > and some payload. > And the APE server calls the client. > > Can anybody of you tell me how this scenario can be handled with APE? > > I know some of the basic commands in APE (CONNECT, JOIN, CHECK and so > on...) but I would like to get more information.... > > Would it be advisable to create a channel per user??? > > TIA > Martin
-- 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/
