Sort of. The intention is not to make a REST API (as JAX-RS already does
that), but because we are going to try and map to 'correct' HTTP semantics
as much as possible it should be very similar to a REST based API, although
the use of JBoss Marshaling means that it can only be used by JDK based
clients.
Stuart
On Wed, May 4, 2016 at 7:55 PM, Nicklas Karlsson <nickarls(a)gmail.com> wrote:
So this will be sort of REST with the exception of the state, transactions
etc? ;-)
(oops, previous post had wrong distribution)
On Wed, May 4, 2016 at 8:50 AM, Stuart Douglas <stuart.w.douglas(a)gmail.com
> wrote:
> Hi everyone,
>
> I have started looking into support for service invocation over HTTP.
> Unlike our existing HTTP upgrade support this will map EJB
> requests/responses directly to HTTP requests and responses, which should
> allow it to be used behind existing load balancers.
>
> I have started an initial description of the protocol at:
>
https://github.com/stuartwdouglas/wildfly-http-client/blob/master/docs/wi...
>
> The intention is to follow HTTP semantics as closely as possible.
> Clustering will be provided in a similar manner to web clustering (i.e. it
> will require a load balancer, and work in a similar manner to web
> clustering).
>
> There is still plenty work that needs to be done (especially around
> security), so if anyone has any feedback let me know.
>
> Stuart
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Nicklas Karlsson, +358 40 5062266
Vaakunatie 10 as 7, 20780 Kaarina
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev