web applications - Architecture Question: Web Service - Multiple client types -


I'm thinking about a certain application. There should be a database-driven back-end and clients can: WebServer service through the SOAP requests (via HTTP / S and XHTML / JS), applications (Windows, Mac, mobile device).

I thought about designing back end in layers.

The initial layer will be of the database, of course. Above this, the web service server, able to talk to SOAP-enabled customers, to read and write data in a database. For those customers, the application will reference the customer and SOAP will be used only when it is necessary to read or write data from the application backend.

I was thinking about the browser presentation layer should it use the level of web services? Or just use the database directly to fulfill the requests made by web browser clients?

Use a normal API Web service is a cover around the web front-end so that He could also use this API. Try to keep as much code as possible within the shared API. Try to avoid multiple code paths that do the same thing on the same database.

It is possible to create front-end at the top of web services, but only if you are using the appropriate Javascript Toolkit (like Dojo, ExtJS). It likes writing javascript whether it's right for your project or not. I create all my web apps in this way, but then I like writing javascript.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -