That looks great, how it should be! One thing I'm not clear on from an architectural point of view is to use that it looks like my controllers have to inherit from the Rpc5AppController and model, which implies to me that those controllers become dedicated to rpc calls. I can't see how to prevent conflict between web and rpc calls. In your example, you have a function called 'hello', but no way to distinguish it from a function with the same name that would be called in a web interface. I think this is what the routing features are about (I've not quite got my head around them yet), so that a single controller can deal with both separate web and xmlrpc functions with the same external name (e.g. /things/function and /xmlrpc/things/function would call function() and xmlrpc_function() respectively. Or is there some way of having two controllers for a given model - one for web, one for rpc? I think I need to re-read the routing manual...
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
