Abstract
Chapter 9 introduced you to web services, and Chapter 11 introduced you to remoting—both of which allow you to develop distributed applications. Web services are mainly used when you wish to communicate across the Internet, whereas remoting is preferred in intranet scenarios. However, in most real-world cases, you need to decide between web services and remoting well in advance because your choice affects your development process. For example, if you decide to use web services, their proxies and XML serialization come into the picture, whereas if you decide to use remoting, activation type and binary serialization come into the picture. At times these differences can prove to be painful. Imagine, for example, that you begin the development with remoting in mind and the application is developed and deployed in a production environment. After a few months, you want to replace remoting components with web services. Can you do that without changing anything in the client application? In most cases, the answer will be a resounding no.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
