Documentation - OSL Monitor

> home

These docs should users enable to modify the oslmon and to include new moduls or to use the moduls for their own purposes+

Modules

RSS-Feed: http://wiki.osuosl.org/display/oslmon/RSS-Feed

Pictures-Slideshow: http://wiki.osuosl.org/display/oslmon/picture-module

WebServices / JIRA-Module: http://wiki.osuosl.org/display/oslmon/WebServices

Core-Api

Thru the Core Api all encoding/serialization is done. This is all handled by one PHP-Class on the Serverside and one Laszlo-Class on Client Side. So someone could easily implement other encodings or a binary modus.

(( At the moment all serialisation from server to client is XML and all communication from client so server uses the "serialize" function of PHP. So basically the Laszlo/Flash/Javasrcipt-serializer is a derivative of the PHP "serialize" Function ( http://www.php.net/serialize ). )) This is the old "deprecated" type

Now serialization is down in an XML-manner. From Server to Client and the way round. This solves a lot of issues espacially the encoding problem from Server to Client. Now everything is UTF-8 encoded.

An Client request to Call a method looks like that now (Thats in the POST-Request):

<lzrequest>
    <header>
        <class>ClassName</class>
        <method>MethodName</method>
    </header>
    <body>
        <param>args0</param>
        <param>args1</param>
        <param>args2</param>
        <param>args3</param>
    </body>
</lzrequest>

Logging

You can log all from everywhere using following syntax: new logging(key,param)

It will all be written to the file logefile.txt: http://bigscreen.osuosl.org/oslmon/dev/logfile.txt

There is also an Conf-Value to autolog alle incoming request with the requesting-IP.