-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add Remote UDP extension #515 #538
Conversation
Co-authored-by: Stefaan Lippens <[email protected]>
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.
some final notes, but I think the core is fine to merge as-is
|
||
### Error Handling | ||
|
||
The following error SHOULD be reported if the namespace can't be resolved: |
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.
What if the URL can be resolved, but the document does not fit? e.g. it's not JSON, it does not follow expected schema, it doesn't contain a process_graph
property, ...?
Shouldn't this also be a ProcessNamespaceInvalid
?
Or would that be for standard errors like ProcessInvalid
, ProcessGraphMissing
? Note however that these don't have placeholders like for a reason, so that could lead to poor error messages
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.
Yeah, I guess that should fallback to the standard errors. Generally, back-ends can also define own error messages and codes. If specific common cases occur that are not covered and need a reason, we can fine-tune this later. Please give feedback :-)
Implements an extension to enable loading user-defined processes that are hosted externally through the process namespace into process graphs.
Closes #515