Hi Przemek, I went along implementing custom RPC filters (as .hrb modules) in hbnetiosrv, but I realized half-way that I totally misunderstood current implementation.
I was under the impression that NETIO_RPCFUNC() is a server side feature (since it's implemented in netiosrv.c), but as far as I could derive from source and tests, it's a client-side one. The idea is that I'm creating a server .exe (hbnetiosrv) with all functions linked in (like hbrun) and I load a filter .hrb which will process all incoming RPC requests and either answer them or deny them. This would ensure that only controlled set of functions are executed on server and it also makes it possible to use one generic hbnetiosrv executable to serve different apps with different needs by loading server-side functionality with: hbnetiosrv -rpc=mysrvmodul.hrb Is this possible to do, or am I missing something in my observations here? [ Doing filtering on the client side looks like a very risky solution, since by getting hold of connection parameters (ip+port+pw), anyone can write an app to do anything on the server. ] Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
