Hi,
Currently SCDL location is modelled as a URL in CompositeImplementation
class. This works ok as long as the SCDL is loaded from a URL. However, with
the stuff I am working on with federated assembly, an SCDL may be
transported into the runtime through the discovery mechanism and thw SCDL
contents may be materialized fully in memory. I was wondering whether we
need a higher-level abstraction than URL or stick with URL and write custom
protocol handlers were the source for the URL is not a standard one (an
in-memory byte array for example).
To give a bit of context, I have been thinking of using the existing
deployer/loader/builder framwork that is used for local deployment in the
federated scenario as well.
Thanks
Meeraj
_________________________________________________________________
MSN Hotmail is evolving check out the new Windows Live Mail
http://ideas.live.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
