Bill Moseley wrote: > On Sun, Oct 14, 2007 at 08:38:52PM +0100, Matt S Trout wrote: >> Catalyst::Plugin::Server is what was going to be the community-designed new >> Plugin::XMLRPC until the namespace owner decided he didn't like the API, >> revoked the PAUSE bits for the ::Server authors and released his own >> one-day-hack rewrite with no reference to any of the design work done. So >> we picked a new namespace and went ahead with ::Server anyway. > > Not sure I followed all of that. I was confused about which namespace > you were referring to, but I see you responded about that in another > thread. > > > I have a more general Catalyst question about Catalyst::Plugin::Server's > design. > > Catalyst::Plugin::Server::XMLRPC uses prepare_action to both parse > the XML *and* to call prepare_action to find the action for the > request. > > Shouldn't the parsing happen earlier in the request (prepare_body)? > > Why do I ask? > > I'm toying with using a ticket based authentication where the token > would be sent in the XMLRPC request body, but use the existing > (cookie-based) session setup that that application uses. >
Using cookies for XMLRPC is considered bad form - most clients that talk to XMLRPC wont have a cookie jar. _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ Dev site: http://dev.catalyst.perl.org/