Home | Trees | Index | Help |
|
---|
Package g4ds :: Module messagewrapper :: Class MessageWrapper |
|
GenericWrapper
--+
|
MessageWrapper
Method Summary | |
---|---|
Yet empty Constructor. | |
String , String ,
String
|
Unwraps a control message and returns the data as to be passed to the service. |
String ; String
|
Extracts the cipher text and the name of the algorithm from an encrypted G4DS message chunk. |
String ; String ; String ;
String ; String
|
Extracts the message, the signature and the name of the algorithm from a G4DS signature message chunk. |
String , xml.dom.Node
|
Processes a G4DS XML message and extracts and returns its content. |
Processes a G4DS XML plain message and extracts and returns its content. | |
String , String ,
String
|
Unwraps a service message and returns the data as to be passed to the service. |
String
|
Wraps a message (String of any type (not only XML)) into a G4DS Control message. |
String ; xml.dom.Document ;
xml.dom.Element
|
Wraps an encrypted message chunk into a valid XML node. |
String ; xml.dom.Document ;
xml.dom.Element
|
Wraps the message together with the signature into a signed G4DS message chunk. |
String ; xml.dom.Document
|
Creates a new XML document, which is a valid G4DS message, containing the data given by node. |
Creates a new G4DS plain message. | |
String
|
Wraps a message (String of any type (not only XML)) into a G4DS Service message. |
Inherited from GenericWrapper :
unwrapActionAndData ,
unwrapArgsAndDatas ,
wrapActionAndData ,
wrapArgsAndDatas
|
Method Details |
---|
__init__(self)
Yet empty Constructor.
|
unwrapControlMessage(self, message)Unwraps a control message and returns the data as to be passed to the service.
|
unwrapForDecryption(self, message)Extracts the cipher text and the name of the algorithm from an encrypted G4DS message chunk. Inverse function towrapForEncryption . Extracts the algorithm
name and the cipher text from the message given.
|
unwrapForValidation(self, message)Extracts the message, the signature and the name of the algorithm from a G4DS signature message chunk. Inverse function towrapForSigning .
|
unwrapG4dsMessage(self, message)Processes a G4DS XML message and extracts and returns its content.
|
unwrapG4dsPlain(self, message)Processes a G4DS XML plain message and extracts and returns its content. |
unwrapServiceMessage(self, message)Unwraps a service message and returns the data as to be passed to the service. The format of the message must be exactly the one as assembled the the functionwrapServiceMessage . Parameters for serive
id and name are taken as text values from the corresponding nodes; the
data itself is extracted from the CDATA section.
|
wrapControlMessage(self, subsystemid, subsystemname, message)Wraps a message (String of any type (not only XML)) into a G4DS Control message.
|
wrapForEncryption(self, message, algName)Wraps an encrypted message chunk into a valid XML node. Encrypted message chunks have to be wrapped into a node named "enc". The name of the encryption algorithm has to be provided in the message itself too, sothat the receiver may choose the appropriate algorithm on its side. The cipher text itself (given asmessage ) is stored into a CDATA
section.
|
wrapForSigning(self, message, signature, algName, senderid, communityid)Wraps the message together with the signature into a signed G4DS message chunk.
|
wrapG4dsMessage(self, node)Creates a new XML document, which is a valid G4DS message, containing the data given by node.
|
wrapG4dsPlain(self, xmltext, messageid, senderid, referenceid=None)Creates a new G4DS plain message. |
wrapServiceMessage(self, appid, appname, message)Wraps a message (String of any type (not only XML)) into a G4DS Service message. The message is put into a CDATA section. This way it might of of any format; and not exclusively XML data. The XML message will look the following way: <service> <serviceid>$appid</serviceid> <servicename>$appname</servicename> <data> <[!CDATA[$message]]> </data> </service>
|
Home | Trees | Index | Help |
|
---|
Generated by Epydoc 2.0 on Sat Oct 22 22:52:47 2005 | http://epydoc.sf.net |