Hello!

So the compromise is this (please confirm):

We make all providers to be pluggable so that there is the vfs-core with maybe one provider for logical testing of the core. And a bunch of provider plugins nicely packaged so that you can just grab the once you need and ignore the rest.


Yes! Though I am not sure what the "core" should be. Maybe we would define the current state as "core"?
VFS in its current packaging is widely used and accepted.


Every new filesystem will be extra packaged and only if the community might find it useful a voting could start to decide if we put it into the core.

And the core will not get any extra quirks because it would be nice when doing something with hibernate through vfs.


YES! And I hope my progress so far made clear that I am definitely would NOT put some "quirks" into VFS.
In fact I would say I am VERY conservative in the stuff I do.
All I have done so far was to stabilize and complete VFS:
*) cache
*) RandomAccessContent
*) compressed files
*) filename parsing
*) plugin
*) now and then (more then then now ;-) ) a little bit documentation


After every change I let VFS settle down a sufficient time period to gave everyone a chance to test and report errors.

So you get the point. Not all that glitters is gold. But sometimes all we really want and need is just the glitter :)


And sometimes we just find some spare minutes and would like to experiment a little bit - even if the result is glitter, maybe for the time being it become gold.


--- Mario


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to