[wp-hackers] WordPress File API Stream Wrapper Support: GSoC 2010 Project Proposal

Otto otto at ottodestruct.com
Fri Apr 9 13:48:55 UTC 2010


- The settings of allow_url_fopen and allow_url_include and similar
are disabled on almost all hosts I've ever used, for security reasons.
This will severely limit the usefulness of the stream wrapping, no?

- What would be the usefulness anyway? We don't really have a "File
API" in WordPress, so I'm not quite seeing how this would benefit
anything. If a plugin wants to use a stream wrapper, it can do so now.
What would this API add, exactly?


On Thu, Apr 8, 2010 at 11:40 PM, Jon Stacey <jon at jonsview.com> wrote:
> Hello,
> I have created a new project proposal for Google Summer of Code this year that I would like to gather some feedback on.
> Abstract:
> The goal of this project is to improve the file handling capabilities of WordPress by making PHP's stream wrapper functionality a part of the File API. PHP stream wrappers allow virtually any type of resource to be represented as a normal file. Stream wrappers will make the implementation details of file management transparent to developers fostering cross plugin interoperability and increasing the flexibility of WordPress.
> Here is a link to the official proposal: http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/jonstacey/t127078510605
> Here is a link to my WP-powered blog with a better formatted proposal: http://jonsview.com/projects/wordpress-project-proposal-file-api-stream-wrapper-support
> I look forward to hearing your thoughts and wisdom!
> Jon Stacey
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list