You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very nice to have the API for handling FTP files support both path to files as strings or already opened file handle resources.
In the underlying API this can be achieved with the ftp_fget and ftp_fput primitives.
Use case:
You have an opened PHP memory stream (or any other stream compatible library) and you are writing the data in it. In the end you want to send all that data to an FTP file.
Currently you will have to save it to a local file, push it to remote server, remove the local file.
With the new feature would be just, pass on the memory stream handle instead of a local path, sparing the overhead of writing and deleting the local files.
Any thoughts on this?
The text was updated successfully, but these errors were encountered:
It would be very nice to have the API for handling FTP files support both path to files as strings or already opened file handle resources.
In the underlying API this can be achieved with the
ftp_fget
andftp_fput
primitives.Use case:
You have an opened PHP memory stream (or any other stream compatible library) and you are writing the data in it. In the end you want to send all that data to an FTP file.
Currently you will have to save it to a local file, push it to remote server, remove the local file.
With the new feature would be just, pass on the memory stream handle instead of a local path, sparing the overhead of writing and deleting the local files.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: