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).
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.
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.
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 ;)
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 |
*------------------------------------------------------*
