September 2006 - jboss-dev-forums

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

anonymous wrote : I don't remember off hand how that is done in Messaging. The lines | callbackServer = CallbackServerFactory.instance.getCallbackServer(serverLocator); | client.addListener(dummyCallbackHandler, callbackServer.getLocator()); | in JMSRemotingConnection create callbackServer as a server and then tell the server side to call it to do push callbacks. If you were just to call | client.addListener(dummyCallbackHandler); | omitting the creation of callbackServer, you would be configuring for pull callbacks, with no server on the client side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973395#3973395 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973395

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by timfox

One of the selling points of remoting was that we could use the remoting API in a consistent way irrespective of the transport which was plugged in. This clearly appears not to be the case with the HTTP transport. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973394#3973394 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973394

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by timfox

What I was expecting is if I make an invocation from the server to the client as is currently the case for delivering messages to clients, then the http transport is clever enough to realise it is only allowed to make invocations from client to server, so uses some kind of polling mechanism to get messages from server to client. This would all be insulated from the user of remoting (us) so we wouldn't have to change any code. If this is is not the case, then it's going to be a lot of grief to change how messaging uses the remoting api to get it to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973391#3973391 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973391

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by timfox

We don't use remoting callbacks in messaging - either push or pull View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973390#3973390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973390

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

Do pull calbacks work with the HTTP transport? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973389#3973389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973389

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

"ovidiu.feodorov(a)jboss.com" wrote : That's not good. | | This is exactly what we DON'T want, a server running on the client side. | | The whole idea with HTTP is that the user does not need to open any inboud client-side firewal ports to receive asynchonous notifications. | | The remoting runtime should poll on the client side, not start a HTTP server. Sorry - I was thinking of push callbacks. There is also a pull callback mechanism, in which the callbacks are retrieved by calling org.jboss.remoting.Client.getCallbacks() Which is used depends on how callbacks are configured by way of the call to org.jboss.remoting.Client.addListener() I don't remember off hand how that is done in Messaging. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973387#3973387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973387

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by clebert.suconic＠jboss.com

I guess when ServerInvoker::setLeasePeriod is set to -1, we shouldn't change any previous estabilished Leases. That would change the behavior of futurue clients... and I guess this is how it's behaving now (if checking the property during setLeasePeriod) BTW when we call LeasePeriod to -1, we didn't have any Lease estabilished yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973386#3973386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973386

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

These details are moot now, since the main reason we need HTTP for, firewall transparency, isn't going to be available anytime soon, not today, in any case, when we intend to release CR5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973385#3973385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973385

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

"timfox" wrote : | I was fed up with the fact that remoting always passed in an ObjectOutput/Input Stream, so I have created new subclasses of ObjectOutput/InputStream called MessagingObjectOutput/InputStream which basically are just a thin wrapper over a straightforward DataOutput/InputStream. | . I don't see how this works. JMSWireFormat is called by Remoting, which passes in an InputStream/OutputStream. How do you get around the socket transport passing in Object streams? Just wondering. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973384#3973384 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973384

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

That's not good. This is exactly what we DON'T want, a server running on the client side. The whole idea with HTTP is that the user does not need to open any inboud client-side firewal ports to receive asynchonous notifications. The remoting runtime should poll on the client side, not start a HTTP server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973383#3973383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973383

19 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2006