Application Lifecycle

jvelilla edited this page Nov 29, 2013 · 3 revisions

EWF Generic Application Lifecyle

The thread of control is initiated by the client (Web Client(Browser) Desktop, other), passed from component to component and finished in the Application to apply our business logic.

Architecture

Application Architecture

Control Flow

Client --> (1-http)--> Server --(2-*GI)--> Connector --(3-EWF)--> Application

Client (share media type (json, xml, html, etc) ) with Service

  1. The client (the Browser or other type of client) initiates the process sending a HTTP request to the server.
  2. The server (Apache, Nino, ningx) receives the request, process it according to its configuration and, if it is the case, dispatches it into a Connector (FCGI, CGI, Nino).
  3. Based on the HTTP operation ( GET, POST, PUT, DELETE).
  • The handler dispatch the business process through an Application Logic/ Business logic.
    1. Custom code per application.
  1. The Application Logic exit and send to the handler the answer.
  2. The handler send the response to the client.
Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.