http request context handling about brokerapi HOT 7 CLOSED

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

from brokerapi.

Please let me know if you require a sample implementation.

from brokerapi.

@lwoydziak do you have an example of when the Cloud Controller would abandon a request? Long running operations are usually handled by async operations.

The timeout for sync operations is 180 seconds, is this the use case you are thinking of? Being able to know when CC times out and being able to cancel the broker operation?

from brokerapi.

@avade: It seems to me that the request could terminate for any network failure--not just when the CC times out. So what should the broker do in the case where the http request terminated (for whatever reason)? If we have the context object, then the broker can decide how to handle it. If we don't, then it will carry on to complete the operation, which is probably not the right thing.

Does that make sense?

Thanks,
-Julian

from brokerapi.

Makes sense, thanks for the explanation.

We would welcome a PR for this feature @lwoydziak

from brokerapi.

See #31

from brokerapi.

Close as pull request addresses this.

from brokerapi.