I'm using kind of an uncommon, maybe even insecure way now. Since I need to send a describing Object anyway I just appended my file as an array of bytes I lookup my TakeStuffEJB via JNDI, and then I'll invoke a remote-method that wants a byte as parameter. I do CRC32 integrity checks on client and server side and it works.
There is a limit to filesize though. Files above 20 MB whill throw a MarshalException("Not Completed") after a while Maybe this is insane because I don't think RMI was designed for filetransfers. But I'll give it a try since the files I'm sending a rarely larger than 1 MB.
I'm using kind of an uncommon, maybe even insecure way now. Since I need to send a describing Object anyway I just appended my file as an array of bytes. I lookup my TakeStuffEJB via JNDI, and then I'll invoke a remote-method that wants a byte as parameter.
I do CRC32 integrity checks on client and server side and it works. There is a limit to filesize though. Files above 20 MB whill throw a MarshalException("Not Completed") after a while.
Maybe this is insane because I don't think RMI was designed for filetransfers. But I'll give it a try since the files I'm sending a rarely larger than 1 MB.
I further improved this with a Stateful Session Bean. With 3 Methods, initNewFileTransfer(FileNameAndInfo) writeChunk(byte data, int NumberOfBytes) finishFileTransfer(long checksum) I secure the order of the methodcalls with a StateEnum and in @PrePassivate I can reset states and free resources. This way I can do a buffered transfer through RMI with any size.
– unR Jun 14 at 10:00.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.