-
Notifications
You must be signed in to change notification settings - Fork 15
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
http/REST support #8
Comments
I like the idea. It could be the basis of a pretty good migration path for wayfin/waif too. it would need to have some semantics, like constructing a message with a path, or url. We could possibly use server sent events too somewhere, but eh. I ran into a bunch of issues with request though, but i have recently had wreck recommended to me. |
@ahdinosaur Definitely thanks! For now I'm looking to have a very thin HTTP/rest thing, hopefully with express/compatibility. Moreover you guys already wrote all those nice modules for http routing :). |
we have the graft-http project now |
so, we need to support HTTP and REST to some extent.
What I think is:
This will create messages with these properties:
req
, the actual readable streamres
, the actual writable streamheaders
statusChan
, Readable channel that can be used to change the status code.What do you think?
The text was updated successfully, but these errors were encountered: