<div dir="ltr"><div>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.<br><br></div>Stuart<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 4, 2016 at 7:55 PM, Nicklas Karlsson <span dir="ltr"><<a href="mailto:nickarls@gmail.com" target="_blank">nickarls@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">So this will be sort of REST with the exception of the state, transactions etc? ;-)</span><br></div><div><span style="font-size:12.8px"><br></span></div></span><div><span style="font-size:12.8px">(oops, previous post had wrong distribution)</span></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, May 4, 2016 at 8:50 AM, Stuart Douglas <span dir="ltr"><<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div>Hi everyone,<br><br></div>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.<br><br></div>I have started an initial description of the protocol at: <a href="https://github.com/stuartwdouglas/wildfly-http-client/blob/master/docs/wire-spec-v1.asciidoc" target="_blank">https://github.com/stuartwdouglas/wildfly-http-client/blob/master/docs/wire-spec-v1.asciidoc</a><br><br></div><div>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). <br><br></div><div>There is still plenty work that needs to be done (especially around security), so if anyone has any feedback let me know.<span><font color="#888888"><br></font></span></div><span><font color="#888888"><div><br></div>Stuart<br><div><div><div><div><br><br></div></div></div></div></font></span></div>
<br></div></div><span class="">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></span></blockquote></div><span class=""><br><br clear="all"><div><br></div>-- <br><div>Nicklas Karlsson, <a href="tel:%2B358%2040%205062266" value="+358405062266" target="_blank">+358 40 5062266</a><div>Vaakunatie 10 as 7, 20780 Kaarina</div></div>
</span></div></div>
<br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div><br></div>