Peter Donald wrote:
> 
> Hi,
> 
> All this talk of cjan/jjan (henceforth called "meep" for ease of typing) as
> services made me think. The notions of directory, local-checker, a fetcher
> and a loader/launcher are very generic. If coded correctly the could be
> generalized to multiple deployment styles (ie not just java .jar files).
> 

Yes, that was where I was drifting a bit.  I was thinking a bit more
today about building a factory model similar to how URLs work -
abstracting the actual resource type away.

Ideas would be great.  I know this is your bag..

> So I would like to ask you when implementing this if you could think about
> definign meep as the envelope of deployment discover, location, retrieval,
> installation and deployment. The actual type of deployment whether it be
> RPMs, .deb files, .jar files, .unr files or whatever is largely independent
> of meeps infrastructure.

even just focusing on .*ar files would give you 26 factories, at the
rate Sun is going....
 
> The content of the envelopes will most likely only be required during
> installation and deployment stages and if done appropriately each
> deployment type could just use a different handler/hook.

And if we keep things small, we can bring the factory in from 'afar' for
the first time, just like any other resource...
 
> So if you consider separating meep out like that with majority of methods
> dealing with resource envelopes rather than directly with resource content
> it could be very useful in some domain I have in mind ;)

Can you tell us?
 
> I just realized something that cjan/jjan could
> 
> checker, a fetcher and
> a loader/launcher
> Cheers,
> 
> Pete
> 
> *------------------------------------------------------*
> | "Computers are useless. They can only give you       |
> |            answers." - Pablo Picasso                 |
> *------------------------------------------------------*

I liked the other sig... :)


-- 
Geir Magnusson Jr.                           [EMAIL PROTECTED]
System and Software Consulting
Developing for the web?  See http://jakarta.apache.org/velocity/
"still climbing up to the shoulders..."

Reply via email to