OCSelot's way of being slim and accessible doesn't stop at documentation: the manual doesn't present every detail of the system, repeating what can just as easily be found in the overview, the examples, and the API. It is there to supplement the other docs by shedding light on aspects otherwise insufficiently covered.
let's briefly recapitulate the main players in an OCSelot application: There's the proxy, a local representative of a remote object, and the subject, the remote object serving the proxy, and there are the client and the server, which function as mediators between the other two.
The four components are linked unidirectionally, like this:
and in this order, from left to right, the manual will deal with them:Class proxies • Creating a class proxy • Constructors • The "rich" constructor • The "pure" constructor • Final classes • Abstract classes - Final methods • Static methods • Virtual constructors • Private, default, and protected methods • Superclass methods • Interface proxies • Creation • Generate interfaces • Class vs. interface proxy: when to use which? • Exceptions Association with the proxy • Creating a client • Remote and local use • The client for remote communication • The client for local communication • Security • Invoking methods on the server Creating a server • Remote and local use • The server for remote communication • The server for local communication • Why use a server locally at all? • Subject maintenance • Security • Invoke server methods from remote • Stop the server Providing a subject • Conditions for association with proxy • Removal • Subject info