|Feedback to Scout framework [message #532162]
||Fri, 07 May 2010 11:36
| Urs Bratschi
Registered: July 2009
Generally I find the approach of the Scout framework quite interesting. The simplicity how you can click together your GUIs and backend component is really nice and efficient. Anyway does scout have some issues in the architecture in my point of view, that could be a killer criteria in the decision for or against Scout.
- The interface between client and server is from technical point of view a webservice, but the formdata objects are serialized and transmitted by a tunneling mechanism. This is not the idea of a webservice. A webservice should be open for other client that wand to use it. This is not really possible in this constellation. It is also not possible to observe the service call from any proxy server.
- The formdata object which is the base of the client/server communication are build from the forms (GUI-Design). According to this there is a service needed to read, store, create and delete the formdata objects. So we have GUI logic on the backend component. If the form changes, there is also a change on the backend service needed. If we have 2 different forms (that shows more or less the same) we will have also 2 different services. The backend should in fact have no knowledge about the implementation in the GUI component.
What my wishes would be for the Scout framework:
- It should be possible to create a real webservice and also generate a WSDL file (for other service users). This would be really cool!
- Between client and server the communication should not be with formdata, but with some kind of business objects. On client side a mapping mechanism from formdata to business objects (and backwards) would be nice.
The advantage of this would also be, that you could use another GUI framework instead the GUI part of scout. The generative approach of forms (like Scout use it) is nice for simple forms (does this exist in the real world?), but for complex constructs always a little bit problematic. I can imagine that a scenario with Scout as framework for client/server communication (I think there is the power of scout) with a own implementation of the forms with SWT, Swing or something else is not so bad.
Powered by FUDForum
. Page generated in 0.02514 seconds