Was not aware that Cap'n Proto RPC got object references over network, need to update my knowledge some day (unfortunately for it, it's also not used by any project I need to interact with)
Persistence wasn't really an issue for me, though I am fully aware how popular in many ways it was to look there.
But ready made naming and discovery are somewhat important when:
- I don't want to mess with details of where specific endpoint is etc - with easily available open source CORBA code, I can setup single CORBA Naming service and provide reference to it from all other components, and while I could do it myself, there's a bit of ease to have a pre-existing IDL and basic "initial naming reference" I can utilise
- discovery is more the use of "Trader" service after establishing the naming part.
Essentially, I have few projects where I want to move the current hodge-podge of hard coded parts into a setup where components can be auto detected and auto configured dynamically with minimal effort from me, and with as wide language support as I can get (including Ada and Common Lisp)
Persistence wasn't really an issue for me, though I am fully aware how popular in many ways it was to look there.
But ready made naming and discovery are somewhat important when:
- I don't want to mess with details of where specific endpoint is etc - with easily available open source CORBA code, I can setup single CORBA Naming service and provide reference to it from all other components, and while I could do it myself, there's a bit of ease to have a pre-existing IDL and basic "initial naming reference" I can utilise
- discovery is more the use of "Trader" service after establishing the naming part.
Essentially, I have few projects where I want to move the current hodge-podge of hard coded parts into a setup where components can be auto detected and auto configured dynamically with minimal effort from me, and with as wide language support as I can get (including Ada and Common Lisp)