This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
I was studying ways do integrate flex with java and i dont whats best integration, remote object or web services.
I know webservices can provide more independence beteween the view and model, but they are very slow >.<
So i just wanna know whats best and what do you use to use to get more performance and maintainability.
the best is always what is needed and what works for you.
if you have restrictions of what network ports are going to be open between the client and server, or even considerations of network address translation problems through home routers.
I prefer to use some kind of RPC, as i have a Java interface, and java implementation of a Java server side and a Java client side. for example, its all in Java, so for maintenance its very elegant to use an IDE for refactoring or navigating the code, quicker for new developers to jump into and work with. But also, I just hate writing WSDL files. There are two reigious schools of thought for web services, one sais the server side code should come first and the WSDL is derived, the other side sais the WSDL should come first and the java code is derived from that. the latter has better control for making things work in a more of a 'lowest common denominator' mode, so as to allow the most fexibility of different kinds of clients to be able to invoke the service. But if you never plan to have some PERL based client invoking your service and always plan to use your java client, then the less-portable to other things to call it concern that comes with using a RPC approach is not a disadvantage.
Im currently investigating the use of JSON-RPC as the messaging protocol for exposing services, instead of XML, and to build Java utilities that serialize Java beans into JSON-RPC request and response messages. So in effect, that is kind of a RPC method, but the underlying messaging protocol is a concise and psudo standard (not as many things currently use JSON to serialize stuff, but it is at least in theory possible for some other language to invoke my service, if there ever was a need to do so).
Error: Keyboard not attached. Press F1 to continue.