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

Ensure existing clients/runtime are in compliance with schemas #22

Open
2 of 8 tasks
jonnor opened this issue Jun 22, 2016 · 0 comments
Open
2 of 8 tasks

Ensure existing clients/runtime are in compliance with schemas #22

jonnor opened this issue Jun 22, 2016 · 0 comments

Comments

@jonnor
Copy link
Contributor

jonnor commented Jun 22, 2016 •
edited by bergie
Loading

Likely we have discrepancies right now as nothing has really checked compliance before.

Clients/tools

  • noflo-ui
  • fbp-spec
  • flowtrace

Runtimes (only listing known maintained ones)

  • MicroFlo
  • NoFlo
  • MsgFlo
  • imgflo
  • pflow

On the client-side, like noflo-ui / fbp-spec etc, I think that flowbased/fbp-protocol-client#50 is the way to go. This will also give some tools for checking that the various runtimes are doing OK, and maybe provide some debugging help if things behave wierdly
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
@jonnor