I'm glad you've learned something, that's the all point of writing this posts.

{quote:jpmsi}
I happen to know from a good source that Mr. Abrantes has done some interesting research on a concept called FileWatcher. It has very strong ties with the hot deploy concept that he is trying to implement, and I''m pretty sure that should be a teaser for us, code junkies, reading these posts.
{quote}

Yes it's true I've implemented a simple file watcher - I actually called file system watcher, since it's monitors a directory in the file system instead of a single file - and the source code along the explanation will be presented in the next post. Like you said it has strong ties with hot deploy, since it's the way we can understan that a class has been modified.

{quote:jpmsi}
I would like, however, to ask (and I'm not so sure this relates to the subject at hand) about the bootstrap. If I understood correctly, this loads the standard VM classes. How does Java implement the low level operations (down the OS integration path) when dealing at this level? I mean… file handling differs from Windows to Linux… Is this integration done at this level or further down the hierarchy?
{quote}

Well I still haven't found much information about that so I can't really point you a reference.\\ 
Although we know that for each OS we'll have a different JVM, being the bootstrap class loader written in native code what probably happens is that it's implementation also reflects integration with the low level directives of the OS. But I'm not sure about that, I'll try to find out about it, and I'll let you know.