Sorry I have the following within my assignment.
"The company's IT director has decided to migrate the existing application to a Java technology based system. Initially, the system will support only the CSRs, although the hope is that this interim step will give them a starting point for migrating the system to the web. The IT director does not anticipate much reuse of the first Java technology system, but intends to use that system as a learning exercise before going on to a web based system"
I read somewhere that if 1 uses sockets for the network, that at the front-end they are not tied to AWT/Swing api. Is it true? Would it be good idea to use sockets to allow existing system, the network and server parts to exist, but all IT director has to do is change the front-end for web-base? (Sorry facts could be wrong)
Hum... in my opinion, if you have an architecture where the components are loosely coupled to each other, then it doesn't make difference if you use RMI or Sockets. If you have everything in their places, then you can build a .jar file with some of the components you created and use it in a Web application (and that's a good example of MVC). Instead of calling your business components from an ActionListener, you could call them from a Servlet. Or even better, you can have an application controller with command strategy before the business components you created for this assignment!
The bottom line is, if you have everything in their places, it doesn't really matter if you are using RMI or Sockets
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
Mark O' Sullivan
posted 10 years ago
Cheers, thanks for that great reply. It's a big help in my understanding of the application.
Your mother is a hamster and your father smells of tiny ads!
Devious Experiments for a Truly Passive Greenhouse!