Wow. Well, this fileDrop is very simple - it slurps in the file contents in a single byte[] and transmits that byte array over the network (via JBoss/Remoting transporting and marshalling) to the server. No chunking or anything.
So, as you can see, the JVM must have enough memory to store the contents of the file in memory (both the client JVM and the server JVM). 2MB should be doable. Getting into the 10s of megabytes will be problematic. That why I think it is ideal for small-to-medium size files like configs and the like. Large jars/wars/ears - you have to be careful. I like the idea of a remote input stream for this kind of thing. WinAmp for JBoss :-) As for performance - dunno. How fast does JBoss/Remoting transmit a several megabyte payload :-) -- John Mazz View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863185#3863185 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863185 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
