-
Notifications
You must be signed in to change notification settings - Fork 26
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
Refactor DO Bindings and extract them to utils #463
Conversation
0ab601a
to
0d31a64
Compare
fdd9d15
to
2b671ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beautiful work! I think the main thing that's left to do is to add a bit of versioning. I'm also not super happy with the custom serialization format for the storage proxy. Ideally we don't have a mixture of serialization formats unless we absolutely have to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant to request changes to make sure we at least address versioning.
7448560
to
d724c41
Compare
3b0d2bb
to
653f0f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Great work.
My one suggestion would be to add a version prefix to the path of the request from the edge service to the storage proxy. capnproto only solves the versioning problem if we decide to always use capnproto. It's still a good idea I think to version the path so that we can change to something else if we needed to. (Hopefully we don't.)
ba5e7cc
to
1fe5a90
Compare
Make a more intuitive and typesafe api for interacting with DOs
c32f833
to
bac1448
Compare
bac1448
to
e1c4e53
Compare
Instead of using global constants to encode the various bindings and methods, define a more intuitive and typesafe api for interacting with DOs.
Also add an abstraction that makes use of these types to implement the communication with the future storage proxy