It may be a good idea if you compile from source and write all the plugins together with the server in the same repository. True, that C++ plugins are probably the most efficient.
But can you imagine us having such a thing?
Here's a ProtectionAreas plugin, download: Windows 32-bit VisualStudio here, Windows 64-bit VisualStudio here, Windows 32-bit Cygwin here, Windows 64-bit Cygwin here, Windows 32-bit MinGW here, Windows 64-bit MinGW here.
It works if you consider that the "plugins" are actually a part of the server without which it won't work - you'll compile everything at once. This is more like a "modules" approach.
If you consider plugins truly "pluggable", it doesn't work so well.
But what do I know, maybe they managed to cook up something more useful.
Oh, they don't have C++ API, they have C API. This works much better, because the ABI is well-defined.
But can you imagine us having such a thing?
Here's a ProtectionAreas plugin, download: Windows 32-bit VisualStudio here, Windows 64-bit VisualStudio here, Windows 32-bit Cygwin here, Windows 64-bit Cygwin here, Windows 32-bit MinGW here, Windows 64-bit MinGW here.
It works if you consider that the "plugins" are actually a part of the server without which it won't work - you'll compile everything at once. This is more like a "modules" approach.
If you consider plugins truly "pluggable", it doesn't work so well.
But what do I know, maybe they managed to cook up something more useful.
Oh, they don't have C++ API, they have C API. This works much better, because the ABI is well-defined.