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

API Corrupt Problem #3

Open
barisyild opened this issue Jul 31, 2020 · 8 comments
Open

API Corrupt Problem #3

barisyild opened this issue Jul 31, 2020 · 8 comments

Comments

@barisyild
Copy link

When we send too many get_task_progress requests, api gets corrupted.

@isrmicha
Copy link

isrmicha commented Aug 4, 2020

too many I/O

try send the request every 2000+ milisecs

@barisyild
Copy link
Author

It is not possible to snyc download progress in 2000 milliseconds.

@barisyild
Copy link
Author

If there are 2 downloads, this number is 4000 ms.

@barisyild
Copy link
Author

PlayStation 4 can go up to 2 (or 3?) downloads at the same time.

@isrmicha
Copy link

isrmicha commented Aug 4, 2020

oh i see, try queue 1 pkg install at time

@barisyild
Copy link
Author

The user has 2 options on my program:
Can follow all the downloads from the program.
or
It can provide downloads while playing games by sacrificing sync progress.

My program is designed to how you want to use it completely.

Unfortunately, if I do what it says, it is not possible to download more than one pkg while playing.

@barisyild
Copy link
Author

All the packages you queue while playing games can be installed without any problems, but if you create a software queue as you said, I cannot assign new pkg to the queue after Remote Package Installer is closed.

@piterq
Copy link

piterq commented Aug 28, 2020

too many I/O

try send the request every 2000+ milisecs

I've got the same problem.
Currently I'm sending request every 5000 ms. Despite this, API gets corrupted (it stops reacting to requests until I restart Remote Package Installer).

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

No branches or pull requests

3 participants