← Back to team overview

acmeattic-devel team mailing list archive

Re: The Web Frontend, the native application Client, the middleware and The Backend

 

On Wednesday 14 July 2010 01:10 AM, suren wrote:
<snip>
1) The Core request processor or the core, which lives on the server
side. The main functionality is to handle disk operations, handles
revisions. Please add more stuff here like how we are going to handle
versioning for binary format and so on . This would be in python

2) The Middleware: Irrespective of the client platform/application, we
hit this layer, which essentially is a API layer to delegate all calls
made to it to the core after enough security checks, gracious error
handling and so on. This is the end point that is available to all the
clients, one web application that can take any related request and
serve back. This could be in Django.

3) The native application or the client app , is the one written in
python handling multiple platforms. Has rich funtionality like
automatic file sync closely tied with the native platform.

4) The Frontend Browser UI or the FE simply, is a browser based thin
client to be a minimal substitute for the native application with as
much features that can be supported by browser predominantly
javascript based.

You've got the basic break-up right. I like the name you've given to the web app part of the server - the Middleware. We will use this term from now on. I would like to focus on the frontend browser UI after we've got most of the other things up and running. It is after all just one of the many clients that should be able to talk to the server.

I will consider this to be your approval for this blueprint - https://blueprints.launchpad.net/acmeattic/+spec/webapp-change-to-api-system

Krishnan, Bharath have given me their (verbal) approval of this blueprint, and so has Karthik, so I will change the status of this blueprint.

--
Aditya.



References