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

Syndicate/js dataspace architecture lagging behind Syndicate/rkt #29

Open
tonyg opened this issue Sep 16, 2017 · 0 comments
Open

Syndicate/js dataspace architecture lagging behind Syndicate/rkt #29

tonyg opened this issue Sep 16, 2017 · 0 comments

Comments

@tonyg
Copy link
Owner

tonyg commented Sep 16, 2017 •
edited
Loading

Syndicate/rkt has been updated to the new inbound/outbound design, while Syndicate/js is still on the old atMeta setup.

Also, the JS Dataspace implementation is still a merged relay+dataspace, unlike the Racket implementation, which has been split out.
@tonyg tonyg changed the title Syndicate/js atMeta doesn't match Syndicate/rkt inbound/outbound Syndicate/js dataspace architecture lagging behind Syndicate/rkt Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tonyg