got a JsonRpcClient and a JsonRpcServer that can send notifications and requests, and receive responses. just need to add about 2000 attributes and everything will be in place. we'll have one socket for LSP->DB, one socket for RD->LSP, and one socket for LSP->RD.
Goal for tonight is to get that db server up, send it a payload via postman/insomnia, glee over getting a response back, and then setup the LSP server's DB client parts.
Exactly - if RD starts a server for an Excel client, and then another for a Word client, we want both LSP server instances to talk to the same database server.
Otherwise we're going to run into issues with cross-process writes to the .db file
tB doesn't need to do this, because they're a standalone editor
hm, I wonder how it handles multiple client instances
meh, probably doesn't have a database backend 😅
just double checking - we decided against spinning up a private database process in the LSP server because we want to share the type library information?
Basically the server implements its RPC endpoints in a class that inherits JsonRpcService, and then on the client side there's a proxy that implements the same interface by sending JsonRpc requests to the server through the JsonRpcClient. It all sounds much more complicated than it really is
VBA Rubberducking
VBA Rubberducking