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

Link to spec #1

Closed
oberstet opened this Issue Oct 21, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@oberstet

oberstet commented Oct 21, 2015

Awesome! WAMP for Haskell;)

The link to the WAMP spec is broken .. would be safer to link to http://wamp-proto.org/spec/ ..

Btw: are you planning to continue this project? Do you want it (already) to be listed at the WAMP Web site?

@mulderr

This comment has been minimized.

Show comment
Hide comment
@mulderr

mulderr Oct 21, 2015

Owner

Hi! Thanks, link fixed.

I am currently occupied with other stuff and doubt I will find the time to push this to the point of usability in production. I believe the client code could be made fairly spec compliant with a bit more work. I have that on my todo list but unfortunatelly not a priority right now.

The router on the other hand is missing a couple key features. Some of the changes needed to fully comply with the spec would require a major redesign of my simplistic, ultra-concurrent approach. If I recall correctly I hit a bit of a wall with ordering guarantees. At this point I don't even have a clear idea how to tackle that. It would probably require some clever (per client?) form of queuing which would ineed complicate the code a lot.

I think it maybe better to err on the side of caution and not list this on the WAMP web site but I don't really have a strong opinion either way. If you do end up including it though, please make sure to mark it as experimental until further notice ;)

Owner

mulderr commented Oct 21, 2015

Hi! Thanks, link fixed.

I am currently occupied with other stuff and doubt I will find the time to push this to the point of usability in production. I believe the client code could be made fairly spec compliant with a bit more work. I have that on my todo list but unfortunatelly not a priority right now.

The router on the other hand is missing a couple key features. Some of the changes needed to fully comply with the spec would require a major redesign of my simplistic, ultra-concurrent approach. If I recall correctly I hit a bit of a wall with ordering guarantees. At this point I don't even have a clear idea how to tackle that. It would probably require some clever (per client?) form of queuing which would ineed complicate the code a lot.

I think it maybe better to err on the side of caution and not list this on the WAMP web site but I don't really have a strong opinion either way. If you do end up including it though, please make sure to mark it as experimental until further notice ;)

@oberstet

This comment has been minimized.

Show comment
Hide comment
@oberstet

oberstet Oct 22, 2015

@mulderr thanks for explaining! I've added the link to http://wamp-proto.org/implementations/, but added wording to mark it as experimental ..

oberstet commented Oct 22, 2015

@mulderr thanks for explaining! I've added the link to http://wamp-proto.org/implementations/, but added wording to mark it as experimental ..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment