Client app uses remoting to connect to server app, hosted elsewhere on webland. Server app accesses a database and returns some data to the client. I think this should be done with SingleCall SAOs.
The remoting class (the one in the DLL shared by both the server and client) shouldn't have the DB connectivity code in it. In fact all it should do is act as an intermediary for the server to handle. All the examples I've found on the internet have the remoting class doing all the donkey work, which means that the client has the DLL with all the functionality in it, which seems wrong to me.
So how do I get the remoting class to talk back to the server? Using delegates/events? So the client calls GetMeSomeData(someParameter), the remoting class simply calls the event handler that the server has set up?