You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature or enhancement request related to a problem or limitation? Please describe
When implementing plug-ins, we should decide whether to implement support in the C++ or the Go layer.
Describe your enhancement idea
There are a few pros and cons to both, and while they aren't all realized, I'll list the ones that come to mind:
C++ plug-ins
Pros
Implement exception handling to prevent plug-ins from affecting rest of server
Plug-ins are usable through zowex
Commands available to extract plug-in info
Cons
Limited to C++ features and DLLs (.so) - no built-in JSON parsing, not many utilities
Golang plug-ins
Pros
Existing Go packages available, such as HashiCorp's go-plugin
More built-in flexibility through Go helper functions
Cons
Exception handling cannot be easily implemented in Go for faulty plug-ins
Plug-ins can't really be used through zowex
Personally, I'm leaning towards C++ for flexibility and use of plug-ins through zowex, but I think this is worth exploring more before settling on that layer 😋
Provide any additional context
Part of plug-in support milestone
The text was updated successfully, but these errors were encountered:
Is your feature or enhancement request related to a problem or limitation? Please describe
When implementing plug-ins, we should decide whether to implement support in the C++ or the Go layer.
Describe your enhancement idea
There are a few pros and cons to both, and while they aren't all realized, I'll list the ones that come to mind:
zowex
.so
) - no built-in JSON parsing, not many utilitieszowex
Personally, I'm leaning towards C++ for flexibility and use of plug-ins through
zowex
, but I think this is worth exploring more before settling on that layer 😋Provide any additional context
Part of plug-in support milestone
The text was updated successfully, but these errors were encountered: