[OGo-MacOSX] How can I have the application running in the background without using the windows server

[Helge Hess]

On 3. Apr 2006, at 11:20 Uhr, Marcus M=FCller wrote:
> Correct. I'm posting to /RPC2 ... thanks for your detailed =20
> explanation.

Maybe we should make the /RPC2 URL a special case which returns the =20
application object. But then maybe not ;-)

> Just for clarity's sake, I then need to add the "categories" to the =20=

> SoObjectRequestHandler object, i.e.:

Yes, RPC2 is a registered request handler (the SoApplication -=20
lookupName:inContext: will try to resolve names by calling -=20
handlerForKey:).

> --- snip ---
>   categories =3D {
>     SoObjectRequestHandler =3D {

Yup, this is messy. Just define a proper object which is your XML-RPC =20=

API and attach that to the application object. Actually it might even =20=

be possible to use "RPC2" as a key for that object, like:

   categories =3D {
     SoApplication =3D {
       slots =3D {
         RPC2 =3D {
           defaultAccess =3D allow;
           protectedBy   =3D "<public>";
           valueClass    =3D ZNeKAPI;
         };
       };
     };
   };
   classes =3D {
     ZNeKAPI =3D {
       methods =3D {
>         "system.listMethods" =3D {
>           protectedBy =3D "View";
>           actionClass =3D "BMSOPEAction";
>           actionName  =3D "listSystemMethods";
>           arguments   =3D { positionalKeys =3D ( ); };
>         };
>       };
     };
   };

Might work, didn't try.

> I see. This really offers quite some flexibility, although I can't =20
> think of a situation where this might be very useful.

Hu? This allows you to properly package your API. Like

   events
     addEvent
     deleteEvent
   tasks
     addTask
     deleteTask

Obviously you don't want to put your whole XML-RPC API in just a =20
single object/class.

A bit more obscure is the ability to address individual objects with =20
XML-RPC. But still quite cool IMHO.

Greets,
   Helge
--=20
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org