"scott.stark(a)jboss.org" wrote : That saves bytes, but whether or not its going
to work depends on the url being usable on the target jvm deserializing the file. I
suppose that is true regardless of how serialization is done.
|
I think this is the right way to do it anyway.
Since you are really forcing structure re-creation on target jvm.
Where in the case of serializing full VirtualFile, you're depending on the impl
details - which in our case you might even get wrong info due to in-memory handling of
nested zips, or by-passing some permission control that is enforced on server side.
If you would like to have full structure already present, I don't think you would gain
much, since you would then 'pay' huge on transport, instead of at re-creation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159258#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...