Re: PaxWeb: WebSocketTracker and Object

czw., 17 sty 2019 o 14:35 Jérémie Brébec napisał(a): > Thanks ! > > By the way, the features processors you introduced in Karaf 4.2 is helping > me a lot with this kind of patch :-) > I'm glad it's useful ;) regards Grzegorz Grzybek > > Le jeudi 17 janvier 2019 14:32:12 UTC+1, Grzegorz

Re: PaxWeb: WebSocketTracker and Object

Thanks ! By the way, the features processors you introduced in Karaf 4.2 is helping me a lot with this kind of patch :-) Le jeudi 17 janvier 2019 14:32:12 UTC+1, Grzegorz Grzybek a écrit : > > Hi > > I reviewed PAXWEB-1119 and understood it. CMPN R7 Http Whiteboard spec > (chapter 140) doesn't

Re: PaxWeb: WebSocketTracker and Object

Hi I reviewed PAXWEB-1119 and understood it. CMPN R7 Http Whiteboard spec (chapter 140) doesn't say anything about websockets. So I'm fine with forcing users to register WebSockets with "(websocket=true)" flag. If websocket endpoint can be (thank you very much JavaEE! - or maybe OSGi should add

Re: PaxWeb: WebSocketTracker and Object

Hello Achim - any reason why this was not merged? Something's missing? regards Grzegorz Grzybek czw., 17 sty 2019 o 13:36 Jérémie Brébec napisał(a): > I reopen (again) an old thread : Is there a plan to merge PAXWEB-1119 into > master/7.2.x ? I have to cherry pick the patch/rebuild paxweb on

Re: PaxWeb: WebSocketTracker and Object

I reopen (again) an old thread : Is there a plan to merge PAXWEB-1119 into master/7.2.x ? I have to cherry pick the patch/rebuild paxweb on every upgrade. Le mardi 8 août 2017 08:24:24 UTC+2, Achim Nierbeck a écrit : > > Hi, > > yes you're right using a non official osgi flag isn't good. >

Re: PaxWeb: WebSocketTracker and Object

BTW, just created the following improvement: https://ops4j1.jira.com/browse/PAXWEB-1119 2017-08-07 18:22 GMT+02:00 Achim Nierbeck : > Hi, > > the problem I see with this is, if one registers a WebSocket as Service, > it usually doesn't need to be of a special Interface

Re: PaxWeb: WebSocketTracker and Object

Hi, the problem I see with this is, if one registers a WebSocket as Service, it usually doesn't need to be of a special Interface ... I can see that a property might help. Will think about this a bit more. Right now you can't disable it. regards, Achim 2017-08-07 14:00 GMT+02:00 Jérémie