« Return to Thread: Asynchronous transport for permanent connections

Re: Asynchronous transport for permanent connections

by Marco D'Alia :: Rate this Message:

Reply to Author | View in Thread

I totally agree,
In that piece of code there is also the problem that the endpoint uri in
the reply-to shoud match exactly the one in the inbound endpoint.

In addSession, getSession ecc the URI can be removed, and use instead a
global hashmap, but it is required in hasServer(..)

Andrew Perepelytsya ha scritto:

> If there's gonna be a follow up, I'll start. Minor things, but this
> one should be addressed first-hand, IMO:
>
> MinaConnector uses URIs as keys for the ConcurrentHashMap. I try to
> avoid URIs as plague, it's just unfixable, period. Have a look at
> http://www.intertwingly.net/blog/2004/07/31/URI-Equivalence ,
> especially the first comment about RFC 2616.
>
> Andrew
>
> On 3/6/07, *Andrew Perepelytsya* <aperepel@...
> <mailto:aperepel@...>> wrote:
>
>     Marco,
>
>     I can't find a direct SVN link to checkout everything, Trac never
>     displays it in the UI. Could you please post one (read-only is ok)?
>
>     Andrew
>
>


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

 « Return to Thread: Asynchronous transport for permanent connections