Re: Data Structure between client and server
In case of having separate model for client and server, use dozer mapper which would map the data from source class to destination the only prerequisite would be the data member names should be same. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Data Structure between client and server
I think use the most simple approach is better. So, if share structure data is simple and enough, use it. I take this approach 2011/4/13 Angelo Brandimarte > I have just started working with GWT, for an University Project. I > have to create a classic client-server sistem. > The client and the server must communicate exchanging some > information. > The server uses data structures to maintain a user model and to > execute basic internal functionalities. > The client uses similar data structures to maintain alignment with the > model in the server. > Is it a good idea to have the client and the server use the same data > structures, and use these structures as the information exchange, > putting them in the shared package, or would it be better to use a > different set of data structures? > Which is the best and commonly solution to this problem? > Thanks in advance > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://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 google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Data Structure between client and server
I have just started working with GWT, for an University Project. I have to create a classic client-server sistem. The client and the server must communicate exchanging some information. The server uses data structures to maintain a user model and to execute basic internal functionalities. The client uses similar data structures to maintain alignment with the model in the server. Is it a good idea to have the client and the server use the same data structures, and use these structures as the information exchange, putting them in the shared package, or would it be better to use a different set of data structures? Which is the best and commonly solution to this problem? Thanks in advance -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
