Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added stream feature to AwsS3 adapter. #334

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jskarpe
Copy link

@jskarpe jskarpe commented Apr 12, 2015

This remove issues with out of memory on large files, and optimize delivery path to clients.


This change is Reviewable

of memory on large files, and optimize delivery path to client.
private $fileHandle;
protected $path;
protected $mode;
protected $fileHandle;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks wrong to me

Copy link
Author

@jskarpe jskarpe Sep 20, 2015 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Making things protected means they become extension points which need to be taken into account for backward compatibility. And extension points by inheritance are the worse ones regarding BC layers (we implement BC layers in Symfony since years, and the ones involving inheritance and BC for protected things have always been the worse ones to implement)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So what's the fix? Copy everything over?

On Sun, Sep 20, 2015 at 8:32 AM, Christophe Coevoet <
[email protected]> wrote:

In src/Gaufrette/Stream/Local.php
#334 (comment):

@@ -12,9 +12,9 @@
*/
class Local implements Stream
{

  • private $path;
  • private $mode;
  • private $fileHandle;
  • protected $path;
  • protected $mode;
  • protected $fileHandle;

Making things protected means they become extension points which need to
be taken into account for backward compatibility. And extension points by
inheritance are the worse ones regarding BC layers (we implement BC layers
in Symfony since years, and the ones involving inheritance and BC for
protected things have always been the worse ones to implement)


Reply to this email directly or view it on GitHub
https://github.com/KnpLabs/Gaufrette/pull/334/files#r39927186.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants