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.

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

non-API compliant UDP behaviour #353

Open
jdries opened this issue Jan 9, 2025 · 0 comments
Open

non-API compliant UDP behaviour #353

jdries opened this issue Jan 9, 2025 · 0 comments

Comments

@jdries
Copy link
Contributor

jdries commented Jan 9, 2025

See first commit in this issue, due to a major performance and robustness problem in operations, I now gave predefined processes precedence over udp's. This avoids expensive udp lookups.

We need to further improve upon this quick solution.

Either we respect the API, and implement some caching of UDP names in the registry. This would not be super difficult, and allows us to respect the API.

The other solution is to double check if a user saves a udp, if the name is perhaps not a predefined process name, and throw an error instead of storing the UDP. That would make our backend more strict than what the API prescribes, but avoids ugly situations. I prefer this solution.

jdries added a commit that referenced this issue Jan 9, 2025
jdries added a commit that referenced this issue Jan 9, 2025
@jdries jdries removed their assignment Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant