Ok, I finally had opportunity to work on this topic a little bit. I first used several hours (or maybe even couple of days) trying to implement 'my vision' of the 'perfect' filesystem into Gaufrette but quite soon noticed that to make the improvements I wished for would have required too many BC breaks (and, thus, heavy refactoring of tests). So, finally, I decided to create my own yet-another-filesystem lib (see link). I think that best illustrates the direction I'd see best to go for.
https://github.com/Rohea/FileStorage The main difference between my FileStorage and Gaufrette is the heavier utilization of library's own File object and its Adapter specific subclasses. This makes it easier to handle certain problems (such as metadata stuff) a bit more elegantly imo. Also, it's now possible to simplify the API of the FileStorage class when some functionalities such as getting the md5 hash can be included in the File object. Check it out and give some feedback if you can. Ps. I know there are no tests yet. I'm a bad person, I know :) -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
