Hi,

About REST or JSON, it is up to you to choose.
I would personally prefer JSON because it is a serialization format and look 
like a more generic way to talk and receive info to the server.
Also, communicating to the server is only a partial view of what need to be 
done.
Don't forget RPC, RPC look more "serious" to me using JSON.
Anyway, it is doable using REST.

Using JSON RPC, you are more standard and could imagine to plug other server 
like Java one.
Again, this is also doable using REST architecture but REST is more URL/web 
oriented while JSON RPC is more about remote procedure call like in RPC :-)

A parenthesis about Delphi, I would not advice to choose one language backend 
only for PDF generation but I'm sure you'll have plenty other good reasons.

About the port.
OK, you need one port.
If you talk to your server using port 81 but why would you need to use the port 
80 from the client side ?

If your thinking about building a 3 tier architecture where static file are 
served via Apache on port 80 and your server replying for dynalic queries on 
81, I suggest the following :
stick to 80 and open only 80. This is the only standard way from proxy and 
firewall point of view.
Then, delegate from Apache to your server internally so all "dynamic request" 
goes to 80 and are then deletage to 81 by Apache.

We're doing that in Java using AJP protocol. This is hidden in the server.
Apache that use 80 and only 80 from outside.
apache delegate to Tomcat 8080  internally but that port is close in the server 
firewall.

I would strongly advice you to start without that kind of optimizations.
Use 81 and only 81 with your Delphi server.
Later on, when everything will work, you will think to more static resources to 
Apache 80 and the delegation in Apache config.
So, you can start by serving the static resources (client side js, images, ...) 
with your Delphi dynamic server.

Hope this helps.

On 23 déc. 2010, at 17:59, slah wrote:

> 
> Hello,
> 
> I'd like to build my backend server using Delphi (due to options I'll have
> regarding PDF generation, etc) and I wonder what works better with qooxdoo,
> a JSON-RPC server similar to the PHP one provided or a REST backend?
> 
> another question is: my backend server will run on port 81 on the same host
> as the web server which listens on port 80. My users are behind a firewall,
> do they need access to port 81 to use my application or not?
> 
> Thank you
> -- 
> View this message in context: 
> http://qooxdoo.678.n2.nabble.com/which-better-for-qooxdoo-JSON-RPC-REST-and-hosting-wonders-tp5862420p5862420.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and, 
> should the need arise, upgrade to a full multi-node Oracle RAC database 
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to