the exchange of information between client and server is done most simply by html, the server performs formatting and the client reads the result.
for a dynamic exchange can be done, the client must interact with data in a form that will be sent to the server, which may make some local spots using macros.
for a dynamic exchange can be done, the client must interact with data in a form that will be sent to the server, which may make some local spots using macros.
on the client, dynamic actions are typically done in javascript, but it is not possible to make shares available to fault the integrity of the client, except when using pure Java which is not recommended.
schematically:
in a restaurant a customer can simply order a typical dish on the menu displayed, the server takes the order and have performed in the kitchen you need for the client to eat. ->> simple usage of html
the customer can also request certain features (such as the type of cooking, with variations in the accompaniment, the cook to be able to adapt ---> use of form and macros
the client must be able to season the meal according to the present context on the table -> Using javascript
in all cases the server is a passive actor, against the client, the server can not reverse roles unless the client agrees to its peril --> for this, the client must activate a java plateform on his machine
