Hi, conceptionelly PDF, XLS and eMails are just an other client / presentation of your domain object/model.
The problem with (classical) web technology is, that the lack of a clean architectural separation. Recently I called classical web technology being a: Real fat client living on a server using browsers as (X-like) display servers. With GWT and Ajax thing become clearer but not continuously. Ajax is great in focussing on real business data instead of transporting (html-) GUIs. Ajax did not really help with images and documents. Classical HTTP deals better with images. To bring to a point, when getting a PDF, XLS your client lives no more in the browser but on your server. Stefan Bachert http://gwtworld.de On 23 Mai, 18:20, VladS <[email protected]> wrote: > It is not so simple with server and client separation. > > For example reports (PDF, XLS). You can't do them on client to the > server should be made aware of user language and presumably have the > same translational table as client does. > > Other type of server-side code with i18n are e-mail messages. > > The exceptions messages thrown from server to client are arguable... > > On May 23, 11:00 am, Stefan Bachert <[email protected]> wrote: > > > Hi, > > > Control and View live on the client > > Model live on the server. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
