> http://web.mit.edu/kpkoch/Public/CCAPI-Windows-Design.html.
A few questions: 0) Is this proposal for a single CCAPI server that serves multiple users? 1) IIRC, the Windows RPC implementation makes it easy to detect client disconnects. I'm pretty sure that the existing (single user) ccapi implementation takes care of this. So there should be no need for the keep-alive and SST stuff. 2) What is the purpose of the CCAPI UUID endpoint? Is it strictly for keep-alive? Otherwise, I do not see the need. Why does the CCPAI client need to act like a server? Is it supposed to get callbacks from the server? 3) What does the server use for LSID? This is supposed to by a system-wide server, right? Why doesn't the server just have a single endpoint? Am I missing something? 4) Why are the messages encoded and then sent over RPC? Is this because the OS-independent code does its own marshalling? 5) I did not understand the "lock" bit in " How is the request handled in the server and the reply sent to the client?" Which locks is this referring to? 6) Can we add pointer to other relevant specs? In particular, which CCAPI version does this refer to? - Danilo _______________________________________________ kfwdev mailing list kfwdev@mit.edu http://mailman.mit.edu/mailman/listinfo/kfwdev
