We could do something like that, yeah. I was thinking over the weekend
that we really should be mimicking the servlet spec here since we're
solving the same problem. Can you file that issue alexey? I'll see
what I can do.
On 11/11/10 12:24 PM, Oleksiy Stashok wrote:
> Hi Justin,
>
> I propose to implement simple URI mapping and make the
> isApplicationRequest(...) method empty by default (return false) so
> atmosphere apps. will be able to implement it, if required.
> So when websockets handshake data comes - we lookup the corresponding
> application by request URL, if not found - we iterate throw the
> websocket apps and asking explicitly if it's "your" request.
>
> What do you think?
>
> WBR,
> Alexey.
>
>
> On Nov 11, 2010, at 18:18 , Justin Lee wrote:
>
>> It came up from problems with atmosphere integration and supporting
>> dynamic URL mapping. In the simple case, that can be a simple
>> equality check on the URI. In others, like the atmosphere uses
>> cases, they needed something more complicated for portability.
>>
>> On 11/11/10 11:35 AM, chris_at_hurstonline.co.uk wrote:
>>> I had a working websockets app, accidently got a glassfish update and
>>> now have to implement this, what criteria should I be using for
>>> returning true or false ?
>>>
>>> What is meant by an application request as opposed to any other request
>>> ? What is an example of an input where I should return true and another
>>> where I should return false ?
>