river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: Dependencies - The Good, Bad & Ugly & Future Possibilities
Date Fri, 12 Feb 2010 10:50:45 GMT
Once an interface becomes popular, it means the cracker knows the 
objects they must provide.  We're going to need some good trust models.

Cheers,

Peter.

Sim IJskes - QCG wrote:
> Peter Firmstone wrote:
>
>> The bad news is that ClassLoader's are memory hungry, so we'll soon
>> run out of both network bandwidth and memory when downloading
>> multiple duplicate codebases all providing similar services.
>
> How would an internet deployment work in practice? When you use a
> service you need to know its interface. So how many interfaces are we
> going to standardize? And those services are they similar, or the 
> same? The only benefit to service proxies would be to distribute an 
> updated version, or when its a big one that you only keep it in memory 
> when you use it (and i'm not sure classloaders easily give up codebases).
>
> Code needs to be deployed anyhow. Once at installtime, or when there 
> are updates, or with every invocation of the program. We have 
> 'downloads', java webstart, jini. With every step we gain extra 
> agility(?). What real scenario, use-case are we facilitating here?
>
> Shouldn't we make a few usecases and maybe create a few personas, so 
> we all get a feel for what problem we are solving here?
>
> Gr. Sim
>


Mime
View raw message