On 4/9/13 11:17 AM, Tomi Saarinen wrote:
Hi. Encouraged by Fabien's recent blog post
<http://symfony.com/blog/symfony-2-3-what-s-next>, I thought I'd might
to come out with a little proposal or thought, if you will.
Note that I was talking about existing issues, not new ones ;)
We all know most websites need to store images and other files to some
kind of filesystem. The default option would be server's local
filesystem but there are much more powerful alternatives for developers
who know their stuff, e.g. cloud CDN systems, Mongo GridFS and such. The
thing is, all these systems have their own apis. It means, whenever you
choose to use one, you immediately have to create a hard dependency on
that filesystem's api. This might be ok if you're developing 'just
another bundle for your specific app' but if you're trying to implement
something more generic and more widely usable, you have a problem.
In most cases our file storing needs are actually quite simple. Basic
crud by key/path is something that's always needed. Also querying,
metadata and uri-awareness are something that might get handy sometimes
as many advanced filesystems support them. There are also solutions. I
personally like the approach of Gaufrette
<https://github.com/KnpLabs/Gaufrette> library. The problem is, it's not
a standard in any way. And while all this sweet standardization process
is going on in PHP world, I'd like to see the api of file storages being
standardized at least on some level. I even think that with some
enhancements Gaufrette could probably be used as a starting point.
That's indeed an interesting topic, but that's not something we will
have time to address for Symfony 2.3.
Fabien
-Tomi
--
--
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.
--
--
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.
