Manila RPC Changes 03/23/00

Thu, Mar 23, 2000; by Brent Simmons.

Changes made today to the Manila RPC interface regard saving information about how message content should be rendered. A new struct, the rendererInfo struct, was added as a parameter to two RPC calls. The get-message handler now includes the rendererInfo struct in the struct it returns.

In general, a renderer generates HTML from simpler text. In Frontier, for instance, a renderer may take an outline and generate a table, or a bulleted list, and so on.

rendererInfo struct

This struct contains two items: name and flRenderOnEntry.

name (a string) is the name of a renderer to use on the contents of the message.

flRenderOnEntry, if true, means pass the contents through the renderer as the message is saved.

Updated manila.message.get

The manila.message.get handler returns a struct containing information about the message. Now it also contains a nested struct, the rendererInfo struct.

Updated manila.message.create and manila.message.set

These two RPC handlers now take a new parameter, the rendererInfo struct.