From aa43456d6d52ab2ebbca1c4d5b1b09c2c949776c Mon Sep 17 00:00:00 2001 From: Stephen L Johnson Date: Wed, 29 May 2002 01:47:10 +0000 Subject: [PATCH] added information about the new predata and postdata spong-server modules --- pod/developer-guide.pod | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/pod/developer-guide.pod b/pod/developer-guide.pod index 9710276..34453aa 100755 --- a/pod/developer-guide.pod +++ b/pod/developer-guide.pod @@ -162,8 +162,30 @@ develops a fatal error, it should terminate using the die() or croak() functions depending on ones preference. Modules should just return upon a successful invocation. +NEW + +There are two new types of Spong Server plugin modules: predata and postdata +modules. The predata modules are called just after a message is received but +before the normal Spong processing is done. And a post module is called after +the Server's normal processing. i + +Also in contrast to the old Spong Server data plugin modules all incoming +messages a sent to the new predata and postdata modules, not just status +messages. Predata modules can even flag a message to tell the Spong Server to +drop the message and ignore it. This will allow you a great deal more access +and control of the Server's incoming message processing. + +Modules are called a predictable, controlable order. There are run in the order +of the sorted registry hash keys. This allows you to create modules that have +run dependencies. + +And there is a new API to go along with the new modules. Now parameters are +passed in a Perl hash. This simplifies the module interface to the server. The +message type is determined by the C field. Message hash details are +in the L document. + See L for an example of how to code a -B Server Data Module. +B Server Data Modules =head2 CLIENT MODULES -- 2.30.2