users@grizzly.java.net

Re: CometContext and NIO

From: Richard Corbin <igf1_at_yahoo.com>
Date: Fri, 3 Oct 2008 14:14:04 -0700 (PDT)

Hi Jeanfrancois, I'm gonna open up a project for this, you had mentioned opening it under Grizzly? How might I do that :) I don't see Grizzly as a sub-project option in the project application section.

( I just left the office Ill be back in about 30 mins and then Ill send over what I have so far) But yes to clarify it worked under GF V3 + 1.8.6.1. But upon further thought, I decided that the framework would be better suited to private communication channels , where the server determines whom to send the messages to (based on Subscriptions to Chanel Objects), and client routes the messages to the appropriate client interface.

So , the code that was giving me all those problems is long gone and what I have now is the 1:1 Session:CometContext

--Richard





----- Original Message ----
From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
To: users_at_grizzly.dev.java.net
Sent: Friday, October 3, 2008 4:42:54 PM
Subject: Re: CometContext and NIO

Salut,

Richard Corsale wrote:
> Hi Jeanfrancois, Thanks for the reply.
>
> The thing about the Exception is that there isnt one :) see what happens
> is , I would register a cometHandler with a specific comet context, this
> would work fine , but when I attempt to register one Handler with
> multiple contexts "strange" things would happen, like it would drop
> (seemingly random) Handlers from the same context. also it would fail to
> register new handlers from the same user once I flush and attempt to
> re-register.

Can you share your code (you can send privately if you want)


  so... really its not a specific error its more of a feature :)

:-)


>
> Note: this does not happen on the latest Grizzly only the one that ships
> with GF2 u2 ?

So with 1.8.6 it works fine (just to be clear)?


>
>
> But about my crazzy solution ( which is moot if GF 2.1 is just around
> the corner) and really, just for clarification. am I hosing up the
> thread pool by creating these contexts?

No I don't think so. But I would really like to take a look at what you
are doing exactly. This is an unusual design by it should works :-)

A+

-- Jeanfrancois


>
> --Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
For additional commands, e-mail: users-help_at_grizzly.dev.java.net