File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Java in General and the fly likes Client Server Tech. Application Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Java in General
Bookmark "Client Server Tech. Application" Watch "Client Server Tech. Application" New topic
Author

Client Server Tech. Application

Mohammad wish
Greenhorn

Joined: Oct 11, 2011
Posts: 12
Good Day All,
I have an application that transfer documents between source and destination machines and the transfer document process is controled by server machine , install controler application on the server and install client (agent) application in source and destination machines, server sent notifcation to the source to send document to destination and destination send notifaction to server that it recived the document from the source and he is ready to recive the next document .

why i want this approach ? becuase i do not want the document to be send to the server (controler machine) for performance issue and secuirty issue.

my question which technologies ,Desgin pattaren and technice should i use to implement this approcahe , i know RMI , JMS ,MDB WS etc...

Regards
Mohd.Weshah



Winston Gutkowski
Bartender

Joined: Mar 17, 2011
Posts: 8427
    
  23

Mohammad wish wrote:why i want this approach ? becuase i do not want the document to be send to the server (controler machine) for performance issue and secuirty issue.

Hmmm. Seems to me that a server is likely to be more secure than two clients interacting independently, but it's your choice.

Rather than a design pattern, it seems to me that what you want is a transfer protocol, and there are several.

Simplest is probably SFTP, since it was designed specifically for the purpose, but you could also use HTTPS or even JMS (which I believe can run over HTTPS).

These could be (and usually are) set up to work completely independently, but if you want the server to act as a "referee", you might be able to set it up as a key factory (or verifier) for the exchange. There may even be standard ways to do this with the two protocols I mentioned, but I've never tried it.

Winston


Isn't it funny how there's always time and money enough to do it WRONG?
Articles by Winston can be found here
Mohammad wish
Greenhorn

Joined: Oct 11, 2011
Posts: 12
Thanks Winston ,
i am not asking about transfer protocol i am asking about which technique is the best to control this operation (JMS, MDB , RMI etc..).

server sent notifcation to the source to send document to destination and destination send notifaction to server that it recived the document from the source and he is ready to recive the next document
Winston Gutkowski
Bartender

Joined: Mar 17, 2011
Posts: 8427
    
  23

Mohammad wish wrote:...i am not asking about transfer protocol i am asking about which technique is the best to control this operation (JMS, MDB , RMI etc..)...

Ooof. Blinded by the red.

I suspect any or all will do the trick, and I doubt that there's any "right" way to go. It's much more likely to be determined by
(a) What you're already running/familiar with.
(b) Considerations of security, reliability, synchronicity/asynchronicity.

The question I'd be asking is: does any existing protocol/system already support the model you want? It all seems a bit "busy" to me, but it's quite possible that someone has already written something similar.

Winston
Campbell Ritchie
Sheriff

Joined: Oct 13, 2005
Posts: 40052
    
  28
Winston Gutkowski wrote: . . . Ooof. Blinded by the red. . . .
I’ll get rid of the red text.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Client Server Tech. Application