users@grizzly.java.net

Re: Async or not async, this is the problem

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Mon, 15 Dec 2008 10:22:04 -0500

Salut,

I guess we forgot to reply on that one.

rama wrote:
> Ok, sorry for the obj of mail, i wasn't able to think on nothing of
> better :D
>
>
> Let me try to explain the problem, that i have summarized with this 3
> class.
>
> WebServer.java (just start a ws)
> MyAdapter.java (the adapter)
> Session.java (session manager)
>
> Lest's begin :)
>
> if someone request url push, i need to procede as follow.
> I create a new session for that user (based on a cookie or whatever,
> this is not of our concern)
> then, i check if in session msg list there is something to send, if yes,
> send it, if not, wait until something is ready.

Take a look at:

http://www.nabble.com/-ANN--New-HTTP-API-for-Resuming-Suspending-Request-Response-tc20573149.html#a20573149

>
> Basically, this work like a charm, but i hold a thread until the message
> arrive to session queue.
>
> So, what's happen if i have 100 user that want to ask for their msg?
> i wait forever :(
>
> I have try to take a look to asyncadapter, but honestly, i don't know
> where to start.
> I already have a read of cometd, but was really too much for me :D
>
> Someone can give to me a hint on where to start to take a look to solve
> this problem?

Use the new API and it should works like a charm.

A+

-- Jeanfrancois

>
> Best regards
>
> (i add the java, don't know if is useful or allowed here)
>
> bye!
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net