we have 20000 thousands client.the client may transfer file to each other that file may be .wav.in this situation i like to choose JMS.but my friend suggest RMI which is better excluding synchronous and asynchronous.
Judge a man by his questions rather than his answers --Voltaire
SCJP 1.5 97%
sir i want to sent file either client offline or online.i about to implement in medical transcription domain.so you are suggested JINI.JINI suitable for this situation.
Originally posted by Ulf Dittmer:
Neither JMS nor RMI are particularly well suited to this problem. HAve you looked at P2P architectures, e.g. Jini in the Java space?
Joined: Mar 22, 2005
i want to sent file either client offline or online.i about to implement in medical transcription domain.
I don't understand what this means. Can you rephrase it with more detail?
so you are suggested JINI.JINI suitable for this situation.
I didn't suggest Jini; I asked whether you had investigated P2P architectures (of which Jini is a Java implementation). P2P may or may not be suitable for the problem you're trying to address; I can't tell from your description.
Joined: Jul 19, 2007
My web application containe 25000 thousands of client.Each client want to send .wav file through server,the server will send particular client.This is my application.
I go through JINI .jini is controlled the device and intimate network user whether the device connected with n/w or not.
how will jini help me i my application please tell me
Joined: Mar 22, 2005
If the server controls the sending and receiving of files then it's not really a P2P architecture, and Jini will not be of much help.
I think I still don't understand what the exact nature of the problem is you're facing. Is it transferring files from clients to the server -or from the server to the clients- or something else? Are the problems in the mechanics of how to do it or in the general architecture?
I would suggest two approaches. Both need file to be uploaded on server. Only difference is how it is delivered to user or where file is stored.
1. Email as Attachment Use any POP3 server (e.g. Apache James) and send file as attachment to the second user.
2. Store file in file system on server or as BLOB in database. Have a link which when clicked will download this file. >> 2a. Send this link via email to second user >> 2b. Display this link to second user when he logs into the system >> 2c. Above point (2b) could be extended to notify user by email of available file
I will not recommend either of RMI or JINI for this.
If file is of larger size, I will recommend to write upload servlet on server such that it can accept normal file as well as compressed zip file. Then user can either upload file directly or zip it and then upload. Further more we can also have file upload applet which can automatically zip file before upload.
Also for download file we can check for "Accept" header from client and gzip file before downloading it.