[Design of JBoss ESB] - Re: Http Gateway - requirements please...
by Kevin.Conner@jboss.com
"tfennelly" wrote : So, as far as my understanding goes, there are no differences from a functional point of view (one query aside, which is below). I do have other parts to implement, but the merging of http and ebws is basically done and is done with min impact, as best I could.
Fantastic Tom, thanks.
"tfennelly" wrote : I do want to make sure we're on the same page re what you want the urls for the http gateway endpoints to be. At the moment, I have it as:
|
| | http://{host}/{.esbname}/http/{urlPattern_from_listener_config}
| |
|
| There was also talk of doing something like:
|
| | http://{host}/{.esbname}/http/{service_cat}/{service_name}/{urlPattern_from_listener_config}
| |
|
| It's easy change to the later if that's what you prefer. I wasn't sure.
IIRC the suggestion from Dave was to use the {service_cat}/{service_name} as the default value of the urlPattern so the URL would either be
http://{host}/{.esbname}/http/{service_cat}/{service_name}
or, if a url pattern was specified
http://{host}/{.esbname}/http/{urlPattern_from_listener_config}
There should be something earlier in this thread, let me see if I can find it.
Kev
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246377#4246377
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246377
14 years, 10 months
[Design of EJB 3.0] - Re: Remoting issue
by jaikiran
Hi Ron,
A few questions
1) Is the default destruction delay being maintained programatically within Remoting? I don't see this delay being added within the EJB3 remoting configurations
2) From what i understand in those threads, the issue was a socket being created on every method invocation on a remote EJB3 proxy. The destruction delay tries to fix this by delaying the destruction of the socket (and the subsequent creation of a new one). Did i understand this right?
anonymous wrote : I've been informally suggesting 5 seconds as a reasonable default delay, but I'm wondering if anyone from the EJB3 team has any better intuition.
Assuming, i understood the issue correctly, i guess the ideal timeout really depends on how the end users use the EJB3 proxies. Some users might have this:
someClientMethod()
| {
| // lookup remote bean
| Bean bean = ctx.lookup(...);
| // invoke method
| bean.doSomething(); // creates a socket
|
| // do something that takes a really long time
| waitForUserInputOrSomeOtherTimeConsumingOperation();
|
| // use the earlier proxy again
| bean.doSomeOtherThing(); // creates a socket (again)
| }
|
|
|
Although if the proxy is being used for multiple method invocations within that default timeout then the performance improvement is going to be noticeable.
3) What is the (performance) impact of specifying a very long destruction delay? Does it degrade the performance or introduce any other issues?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246373#4246373
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246373
14 years, 10 months