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
My project is reading clients game log files and outputting results. I have client set location for a text log file for a game they play when they sign up. Currently only the upload occurs when client calls the upload. I want it to be so that once file location is defined/set then both client and server can access file passively without client having to explicitly call upload. So once client is logged in I would have access to file as a streaming read/write that can be open/called at any time. Is this currently possible and I am failing on way to implement or would this be possible as enhancement?
Thank you for reviewing.
The text was updated successfully, but these errors were encountered:
I believe this issue belong to front-end file access/reading
You can store path to file defined by user for later usage, not sure about access to this file without explicit user permission.
This package will accept any File object for upload.
Yes the explicit permission I have issue with and cannot find workaround. I wonder if a way to hack around it or if way to treat like server always has read access. I will close as this isnt issue with package.
My project is reading clients game log files and outputting results. I have client set location for a text log file for a game they play when they sign up. Currently only the upload occurs when client calls the upload. I want it to be so that once file location is defined/set then both client and server can access file passively without client having to explicitly call upload. So once client is logged in I would have access to file as a streaming read/write that can be open/called at any time. Is this currently possible and I am failing on way to implement or would this be possible as enhancement?
Thank you for reviewing.
The text was updated successfully, but these errors were encountered: