I'll give you my opinion based on your description. Or course, this is only one of the various ways you can implement your project.
It would be awesome that other members of the list provide their own implementations so we can compare. I'm creating a client/server learning management system. It will involve > everything from passing objects to multimedia audio/video. I need some > kind of control structure to pass requests to different services on the > handler. This could be implemented as a rich Internet page. Of course you will need a web interface (which you said you don't want) but this way it's already available and ready for you to put together. I was just creating a main handler and having it call an array > of services. But none of this is set in stone. I'm really just learning > it. An example would be a student logs in and a request if made for the > list of courses this student is enrolled in. So my server would return a > list of Course objects to the client. So I have to have a way to route > requests to the proper services. This is normally implemented as a page. You can make this a standard web service using SOAP (which relies on HTTP itself) and make it available for every kind of client, be it or not a web based one. I started to create a action class that > just extends a hashmap that way it was abstract enough to used on future > version. Like JMS message class. Does any of this make sense? I'm sure > others deal with this issue all the time. I even thought about just > copying the JMS message class. Again, you could implement it using a variety of methods, but the web page version makes more sense to me. Regards, Rodrigo
