I developed a web application (works properly) which registers a user to the system and allows user to upload a file to system via https. The client side code is totally developed by using GWT 2.4 and the back end is several servlets. Except the upload code, all the client-server communications are done via using ServiceAsync interface as it is the common practice in GWT. The upload code is based on a form which is communicating with the upload servlet directly.
This project is developed as a course work and my Professor is keen on knowing the underlying architecture of google web toolkit specificly focused on the client-server communication. His question was, "How the client code knows the server's url so that all the communication is done?" His question is legitimate for the serviceAsync interface. I am calling a function on the server side which seems interesting to him and he wants to know the underlying process behind it. For uploading, I just defined uploadForm.setAction(GWT.getModuleBaseURL()+"upload"); where upload is the name of the upload servlet in web.xml. I told him that the compiler generates a .js code which contains all the web application code (whole system developed dynamically) and the url to the servlet is placed in that .js file however the answer did not satisfy him. Please let me know the inner facts of the client-server communication with GWT. Please give me some answers that can help my Professor to understand the service async calls. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/_itNVCEQV3QJ. 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.
