Re: [Springframework-developer] HTTP invoker remoting strategy

[<jue...@we...>]

Yes, it will! I consider it stable enough for inclusion, and am =
immediately gonna use in application projects myself.

It's actually pretty simple and straightforward: Most effort went into =
the design for extensibility. For example, the HTTP invoker stuff shares =
the RemoteInvocationFactory and RemoteInvocationExecutor strategy =
interfaces (which allow to add and interpret additional invocation =
context like user credentials) with the RMI invoker mode of =
RmiServiceExporter and RmiProxyFactoryBean. So even if you use such =
custom invocation context, you still have the drop-in choice between RMI =
invoker and HTTP invoker!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Patrick Peralta
Sent: Tuesday, August 10, 2004 7:22 PM
To: spr...@li...
Subject: Re: [Springframework-developer] HTTP invoker remoting strategy


Very nice!  Will this be included in the 1.1 release?

On Tue, 10 Aug 2004 10:38:13 +0200, j=FCrgen h=F6ller [werk3AT]
<jue...@we...> wrote:
> I've finally committed my new HTTP invoker remoting strategy: It =
resides in the remoting.httpinvoker package.Usage is just like Hessian, =
Burlap, or RMI invoker: Simply define an HttpInvokerServiceExporter on =
the server side, and a corresponding HttpInvokerProxyFactoryBean on the =
client side. Use an HTTP URL just like with Hessian or Burlap, that's =
it.
>=20
> The main difference to Hessian is that this HTTP invoker uses Java =
serialization, just like RMI. It more or less combines the advantages of =
Hessian (HTTP-based, easy to set up) and RMI (full power of Java =
serialization). In particular, it should work nicely with Hibernate =
collections. It's about as fast as Hessian or RMI, so performance should =
not be an issue either.
>=20
> HttpInvokerProxyFactoryBean uses a HttpInvokerRequestExecutor strategy =
for the actual executing of HTTP POST requests. Default is =
SimpleHttpInvokerRequestExecutor, using J2SE's HttpURLConnection (so no =
external library necessary). Alternatively, there's =
CommonsHttpInvokerRequestExecutor which uses Jakarta Commons HttpClient, =
potentially with HTTP authentication, HTTP connection pooling, etc.
>=20
> I've also added the HTTP invoker as further remoting strategy to the =
JPetStore sample app. JPetStore's OrderService now gets exposed via 5 =
different remoting strategies: Hessian, Burlap, HTTP invoker, RMI, and =
JAX-RPC. Accordingly, the sample OrderServiceClient access the backend =
OrderService via all those strategies now. OrderServiceClient also gives =
rough performance measures.
>=20
> Juergen
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer