OLE Server Specification

This page is intended as a full description of the Computer Concepts OLE protocol as seen from the server side. A programmer writing an application should be able to find here all the information required to let the application work as an OLE server. To let the application work as an OLE client, see the OLE Client Specification.

The server
Any application which provides its own file type and is capable of editing such files may set itself up to be an OLE server. To do so it needs to be able to send and accept OLE messages, and announce itself as a server by setting an environment variable for each file type it can handle.

Setting the environment variable

 * For the syntax of the OLEServer$Type_XXX variable see the OLE Client Specification.

The !Boot file of the server should set an OLEServer$Type_XXX variable for each type of file it wishes to serve. The -R value should start the server, and the -N value should be a string which can be recognised by the server as referring to itself. The name of the server application is usually a good choice, possibly extended with some characters to prevent confusion with other servers.

An OLE session
An OLE session will be initiated by a client application. The server simply waits until a request comes in.

Opening the session
A client that wants to open a session will save the data as a temporary file and broadcast an OLEOpenSession User_Message_Recorded (type 18) message. Messages intended for your server will contain the same string at offset +20 as you set in the -N parameter of the environment variable. The message also contains the type of the file that the client wishes to be edited.

If the server recognises the string and the file type, it should acknowledge the message by sending an OLEOpenSessionAck message. It should set up internal data describing the OLE session, read the temporary file (its path is given in the message) and offer it to the user to edit.

File changes
When the user saves the file being edited, the server should send an OLEFileChanged message to the appropriate client. The server can choose to either
 * save the file to the same path as the original (recommended) and send a format 1 message
 * save the modified file to a different temporary location, and send a format 0 message.

Note: though the client is obliged to check if the format of the file is correct, the server should take care to only write valid data.

Closing the edit
When the user closes the file being edited, the server should send an OLECloseSession message to the appropriate client. The server can consider the session closed. (For an exception, see the Format 2 OLEOpenSession message.)

Setup
The server should setup environment variable for each file type it is willing to handle in its !Boot file.

When the server is started, it should be ready to receive OLE messages and have handlers in place for them.

A file changes
Whenever the user saves changes to a file, the server should check its internal data to see if the file is part of an OLE session. If so, it should send an OLEFileChanged message to the client.

Message_OLEFileChanged (&80E1E) ---   SWI Wimp_SendMessage On entry - R0 = 17 (User message) - R1 = ^Block +0 = length of block +4 = task handle of sender (not used on entry) +8 = my_ref (not used on entry) +12 = your_ref = 0 (original message) +16 = message number (&80E1E) +20 = format number format = 0 (saved to a different file) then +24 = Session number +28 = full pathname of data, zero terminated format = 1 (saved to the same file) then +24 = Session number (format used by OLESupport) format > 1 then +24... reserved for future extensions - R2 = Task handle of client

The task handle of the client in R2 and the Session number at offset +24 should be those associated with the file that is edited.

If the server application saves a file to the same path, it should send a format 1 message. If it saves to a different file, it should send a format 0 message, passing the changed path name in the message.

An edit is closed
When the user ends an editing session, usually by closing the editing window, the server should check its internal data to see if the file is part of an OLE session. If so, it should send an OLECloseSession message to the client.

Message_OLECloseSession (&80E23) SWI Wimp_SendMessage On entry - R0 = User message (17) - R1 = ^Block +0 = length of block +4 = task handle of the sender (not used on entry) +8 = my_ref (not used on entry) +12 = your_ref = 0 (original message) +16 = message number (&80E23) +20 = format number format = 0 then +24 = Session number (-1 means all sessions are closing) format > 0 reserved for future extensions - R2 = Task handle of client

The task handle of the client in R2 and the Session number at offset +24 should be those associated with the file that was edited.

The server can consider the session ended and remove any internal data associated with the session. The client will be responsible for the removal of the temporary file.

Alternatively, a server may keep the contents of the edited data in its internal memory and keep the session information in its list, merely marking the session as closed. It can then accept format 2 OLEOpenSession messages for this data in the future.

The server quits
When the server quits (e.g. because the user selects Quit from the menu), it should broadcast an OLECLoseSession message with Session number -1 to inform all clients which may have a session open with it that it should close those sessions. Note that the server does not really need to check if it actually has any sessions open. It can simply broadcast the message and let the clients work out if they have sessions that need to be closed.

Message_OLECloseSession (&80E23) SWI Wimp_SendMessage On entry - R0 = User message (17) - R1 = ^Block +0 = length of block +4 = task handle of sender (not used on entry) +8 = my_ref (not used on entry) +12 = your_ref = 0 (original message) +16 = message number (&80E23) +20 = format number format = 0 then +24 = Session number = -1 (all sessions are closing) format > 0 reserved for future extensions - R2 = 0 (broadcast)

Note: the server should not feel it owns the file and thus should not attempt to delete the file during emergencies.

Format 0 and 1
These messages indicate that a client wishes to start a new OLE session. From the server's point of view there is no difference between a format 0 and a format 1 message.

Message_OLEOpenSession (&80E21) ---    +0 = length of block +4 = task handle of the sender +8 = my_ref +12 = 0   +16 = message number (&80E21) +20 = 16 byte unique name padded with zeros +36 = window handle of display holding file +40 = x offset of data in window +44 = y offset of data in window +48 = format number format = 0 or 1 (edit file) +52 = Session number +56 = file type +60 = full pathname of data, zero terminated format = 2 (re-edit file) +52 = Session number format > 2 (reserved for future expansion)

If an OLEOpenSession message comes in, the server should check that the message is intended for it. If either check fails, the server should simply ignore the message.
 * It should check that the Unique name at +20 is equal to the value of the -N parameter it set in the environment variable(s).
 * It should check that the file type at +56 is a type it wants to handle (as encoded in the name of the environment variable).

If the server wants to handle the session, it should send a copy of the message back as a User_Message (17), with the original my_ref code at +8 copied to the your_ref field, and the message number set to the code for OLEOpenSessionAck (&80E22).

Message_OLEOpenSessionAck (&80E22) --   SWI Wimp_SendMessage On entry - R0 = User message (17) - R1 = ^Block +0 = length of block (unchanged) +4 = task handle of sender (not used on entry) +8 = my_ref (not used on entry) +12 = your_ref: a copy of the my_ref of the OLEOpenSession message +16 = message number (&80E22) +20 The rest of the message unchanged from the OLEOpenSession message - R2 = Task handle of client, from block+4 of the OLEOpenSession message

This will have the following effects:
 * It tells the WIMP that the original recorded message is acknowledged (because my_ref was copied to your_ref), so that message won't bounce back to the client.
 * It sends the new OLEOpenSessionAck message, so the client will know this server has accepted the session.
 * It informs the client of the task handle of the server.

The server can now start editing the file, whose path was given in the message block (at +60). The server should remember the client's task handle (+4) and the Session number (+52), as the combination of these numbers uniquely identifies the session.

Format 2
The client may request to re-edit the same file. It can then send a format 2 message which will inform a server that the user has tried to perform an OLE action on the same data a second time. This gives those servers which allow documents to be closed, but not lost from memory (eg ArtWorks) a chance to reopen an edit window on the data. Note that a message of this format does not include a path for a temporary file created by the client, so this format only works if the server still has the file data in its memory.

Servers which do not keep data from closed edits can simply ignore this message. The client will eventually send a format 0 or 1 OLEOpenSession message, which the server can handle in the normal way.

If a server wants to handle a format 2 request, it should check the client's task handle and the session number to see if it knows the OLE session, and still has the data. If not, the server should ignore the message.

If the server knows the session and still has the data, it can acknowledge the message in the same way as for format 0 and format 1 OLEOpenSession messages, mark the session open in its internal data, and offer the data to the user for editing.

OLECloseSession
These are sent by a client when it abandons the object for which an OLE session is active. For example, a DTP editor (the client in this example) may have a table included in its document. The user wanted to edit the table, so the DTP editor started an OLE session with a server that can handle the table. While this session is going, the user decides to cut the table from the document. This means that the OLE session can be abandoned, and the DTP editor (the client) sends an OLECloseSession to the server with the Session number associated with this session at +24.

In another case, if the client quits, this implies that all the sessions it has open must be closed. To do so, it will broadcast an OLECloseSession message with Session number -1.

Message_OLECloseSession (&80E23) +0 = length of block +4 = task handle of the sender +8 = my_ref +12 = 0   +16 = message number (&80E23) +20 = format number format = 0 then +24 = Session number (-1 means all sessions are closing) format > 0 reserved for future extensions

The server should check the combination of task handle (at +4) and session number (at +24) against the documents it is editing. When a document matches, the server should quit the edit of that file.

If the Session number is -1, the server should quit all edits of documents that are associated with the task handle of the client.

In either case the server should not feel it owns the file associated with a session and thus should not attempt to delete it. Deletion of the file should be left to the client.