What you're talking about doing is potentially extremely dangerous! Elevation city! Even if it's internal, you're not just opening a door you don't want to open -- you're CREATING a door that shouldn't be there.
.NET won't even deserialize mutable objects from other servers unless you turn security settings down -- that's how dangerous it is to accept objects/code/assemblies from the "outside," and interact with them in any way -- much less load and execute them in whole! BAD! ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Mon, Oct 12, 2009 at 11:23 AM, Pat <[email protected]> wrote: > > For the remote clients, I am going to start with using SQL Server to > marshal objects from the server to the clients for execution. > > I had originally envisioned zipping up the object (DLL), it's metadata > and manifest into a single file for transport via a web service. This > was just for simplicity and size. But I see that enabling compression > for the web services served is no big deal. > > My question, therefore, would be is it better to use the compression > built into the service provider, or have everything needed for work in > a single zipped archive? > > I gravitated to the single file work distribution model because it > didn;t require a myriad of web services-one for each type of work. It > seemed best to just have a client ask for work, a single file was > returned, it unzipped it, inspected it, and did the work. > > Thoughts? > > pat > :) >
