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

Handle returns to executing client #4

Closed
mnxfst opened this issue Jan 12, 2012 · 1 comment
Closed

Handle returns to executing client #4

mnxfst opened this issue Jan 12, 2012 · 1 comment
Assignees

Comments

@mnxfst
Copy link
Owner

mnxfst commented Jan 12, 2012

The ptest-server is expected to run in a distributed environment having n parallel ptest-server instances. Since the client needs to know about the (accumulated) results each run produces, there must be a way to return those information to the client.

Since the execution is triggered using a HTTP server call, the results could be included in the response. Unfortunately this works only for a small number of test plan recurrences. Therefore either the client must provide a callback URL the server must be aware or the client needs to constantly poll results from different source (eg. database).

Another way to handle this could be a central ptest-server instance or another dedicated control instance which is ordered to execute a distributed test case, colllects all results, stores them using a unique session identifier and provides the data on a different HTTP call back to the caller. In that case the caller could constantly pull for results and must not provide a callback url.

@ghost ghost assigned mnxfst Jan 12, 2012
@mnxfst
Copy link
Owner Author

mnxfst commented Feb 16, 2012

The client knows when results should be available and requests the values after a defined time-period if there are no results, the client sleeps and comes back later

@mnxfst mnxfst closed this as completed Feb 16, 2012
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

1 participant