[Opensource] Swing client

Fri Jul 5 09:16:09 PDT 2002

Hi Turgay,

Well here are some thoughts about the Client issue:

1) HTTP is not that efficient solution for me. Is is true that SOAP and 
XML-RPC are simple to use but they are not very efficient.
You have to go to XML when you send the data, and then on the client side to 
parse it again and so on.
One of the major advantages of using a remote client is the gain of 
performance - the client will not have to wait every time
you reload the page - for me about 50% of the communication with the server 
is with data that is already with the client -
it has not been displayed the way one wants.

2) The discussion is getting too much into JaWS and etc - the client is not 
ready yet :-)) nor is the server :-). I think
that there are too many unknowns in the Expresso integration and 
client/server communication.

3) When I said RMI I did insist on Java RMI - though it will be nice. It 
could be a simple TCP/IP socket thing and will be limited to sending
Request and responses back and forth. The client will expect a Response 
object and the Server will expect a Request object.
The client will construct its view based on the Inputs, Outputs and 
Transitions and send the user request embedded in the
Request. I ma not a security guru but even if you intercept the client's 
request I do not think taht is is that easy to
figure out what the serialized Request is. Of course everything is possible.

4) Now here is what I meant by bypassing the Expresso security. When you the 
our server get's the user's Request he will
have to deal with Expresso. This is where I am getting lost - I have not had 
the time to go deep there and figure out what is
going on. If you could give me more info on how you implemented you client 
and its communication it will be great.
But you do not have a session to store user's information, plus you do not 
have controller over the Servlet. So if we go
with RMI we have to think how to dispatch the user's request to the 
controller without bypassing Expresso security. Here the
guys from Expresso could be very helpful.

I know I might sound too keen on Objet Oriented Communication but this is 
the most efficient solution - from performance prospective.
And will really give the user's what they want - fast response, low server 
load, less traffic. However I do not discard completely HTTP.

The reference to Java Servlet Programming was not that bad - they provide an 
example of sommunicating via tcp/ip sockets and rmi.
Both could be the possible solution, but RMI could be more beneficial in the 
future if we decide to do more then just passing the Request/Response
For me it is not very clear how would we modify the ActionServlet (or 
replace it).

>From: "Turgay Zengin" <turgay_zengin at hotmail.com>
>Reply-To: opensource at jcorporate.com
>To: opensource at jcorporate.com
>Subject: Re: [Opensource] Swing client
>Date: Fri, 05 Jul 2002 00:12:12 +0300
>
>Hi Tsanko, thanks for clarifying some issues. About your ideas:
>
>-communications: I made a test today and logged into Expresso from a
>standalone client, but I had problems with the Controller so I had to 
>change
>LoginController's processLogin. But this was because that I did not
>send/receive ControllerRequest/ControllerResponse, but a HashMap containing
>name/value pairs. That's a good idea to pass
>ControllerRequest/ControllerResponse, then the Controllers will stay the
>same. But we'll need to keep Expresso class files on the client as well
>then...
>
>-RMI: I did not use RMI before, so I don't know the pros/cons well. Jason
>Hunter's fine book "Java Servlet Programming" describes communication using
>RMI, HTTP, and non-HTTP sockets. (Source code can be downloaded from
>http://www.servlets.com - Chapter 10 is all about applet-servlet
>communication). I was considering using HTTP, but RMI is welcome if I can 
>do
>it and it's worth.
>
>-about bypassing Expresso security: can you please explain what you mean by
>this? I just logged into Expresso from client app today, and the
>LoginController places objects on the session to describe the CurrentLogin,
>so this should not be a problem, Expresso security should behave the same.
>Am I missing something here?
>-protection of the information being passed: very important. I didn't need
>to consider this before, so have no idea how to do (https?)
>
>Hi David,
>Thank you very much for a good explanation of JaWS. I think JaWS is the way
>to go for client side applications.
>Yes, I was considering HTTP communication. And for the servlet, as Tsanko
>said, ControllerRequest/Response can be passed between, so another servlet
>will not be necessary, the same Controllers can be called.
>SOAP (e.g. Web Services) : I have really little idea about what they are -
>can you briefly describe benefits of using SOAP and Web Services for this
>job?
>
>
>
>_________________________________________________________________
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>_______________________________________________
>Opensource mailing list
>Opensource at jcorporate.com
>http://mail.jcorporate.com/mailman/listinfo/opensource
>Archives: http://mail.jcorporate.com/pipermail/opensource/

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com