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.

Sign up for GitHub

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

Jump to bottom

Request promises should reject #16

Closed
hjdivad opened this issue Jun 18, 2013 · 0 comments
Closed

Request promises should reject #16

hjdivad opened this issue Jun 18, 2013 · 0 comments
Assignees
@hjdivad

Comments

@hjdivad
Copy link
Collaborator

hjdivad commented Jun 18, 2013

see also #14 #7
This was referenced Jun 18, 2013
Open
Closed
@ghost ghost assigned hjdivad Jul 9, 2013
hjdivad added a commit that referenced this issue Jul 12, 2013
@hjdivad
Better use of promises with requests.
5e6d8b2 
- Request handlers are not passed a resolver: instead they may return values or
  promises.  It is an EXPERIMENTAL API but they may also throw errors directly
  to indicate unhandled requests.

- `Oasis.connect` triggers an error callback if the initialization message does
  not include the requested capability.  There is one for each corresponding
  API:

  - a third argument, an error callback, can be passed
  - consumers' error functions are invoked
  - if the single string arg API is used, the returned promise will reject.

Fix #14 #16
@hjdivad hjdivad closed this as completed Jul 12, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hjdivad hjdivad

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hjdivad