Hi,
sure, you don't need RPC to interface with a Java Servlet (or any other HTTP
backend).
Conceptually, RPC is not about sending requests and receiving responses.
Instead, you call remote methods which return. Its a way of talking to a remote
process (interprocess communication). If all you need is sending a request and
handling its response, talk plain HTTP.
If you want to use RPC, you may also want to consider JSON-RPC. If you go the
HTTP way, you may want to familiarize yourself with REST.
Am 01.11.2011 um 23:33 schrieb d_dunken:
> Hi,
>
> I was just wondering what the purpose of the RpcJava contribution really is?
> Is it not just possible to use a stanrdard Java Servlet and format the
> response depending on what servlet was being called?
>
> var req = new qx.io.remote.Request(url, "GET", "text/plain");
>
> And use a servlet to just send the resulting content:
> ...
> public void doGet(HttpServletRequest request, HttpServletResponse response)
> throws IOException, ServletException
> {
> response.setContentType("text/plain");
> PrintWriter out = response.getWriter();
> out.println("A Sample String...");
> }
>
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/RpcJava-vs-Java-servlet-tp6953492p6953492.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> RSA® Conference 2012
> Save $700 by Nov 18
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
