Craig Perez wrote on 05/29/13 17:17:
> I think I may have missed something as well? If the GlassFish server downloads
> the application on behalf of the "client" then I'm suggesting a separate
> "sandbox" area for this download purpose. Browsers have download folders where
> things go by default and those are typically separated for each user.
How would this be different than the folder it uses for applications uploaded
from the client?
> Having different permissions, quotas, etc. are not so much about access from
> GlassFish server itself but potentially from other processes/uids in the
> system such that the downloaded content would not be used outside of the
> intended purpose. My suggestion is based on providing potential for more
> flexibly in cases where administrators maybe concerned about resource handling
> and the existing folder may already be sufficient.
Again, I don't understand why this should be treated differently then uploaded
applications, or what advantage there would be for treating it differently.