On Tue, 30 Oct 2001, Robin Berjon wrote: > If anyone feels like undertaking this task, imho the best > first step would be to produce XML::P3P (it's not Apache dependent) > and add Apache::P3P as a wrapper around that that would take care of a > few simple things such as setting the headers properly and so forth.
Hi. Don't normally post or read this list but Leon Brocard pointed this out to me. I've been doing a lot of work for my company on what you talking about. Code is available at: http://2shortplanks.com/temp/P3P-ToCP-0.02.tar.gz. Documentation (html of the pod) is also at http://2shortplanks.com/temp/P3P_ToCP.html This is a beta version of a module that will take a P3P document and create a CP version of it that is suitable for inserting in the HTTP P3P header. This will go up on CPAN very soon, as soon as we've worked out what to call it. I've been in discussion with the modules list about what it should be named (as there are thoughts that it shouldn't go in the XML name space.) Any ideas on this would be appreciated. Apart from that it's pretty much complete (but I really could do with some feedback on the code too.) Some additional documentation regarding P3P and p3p2cp (a command line script to trigger the module) probably could do with being written. As goes for integrating it with apache, I guess the most sensible thing to do would be to parse the P3P policies at start up and cache the headers that should be delivered each request. Hope this is of some help. Mark. -- s'' Mark Fowler London.pm Bath.pm http://www.twoshortplanks.com/ [EMAIL PROTECTED] ';use Term'Cap;$t=Tgetent Term'Cap{};print$t->Tputs(cl);for$w(split/ +/ ){for(0..30){$|=print$t->Tgoto(cm,$_,$y)." $w";select$k,$k,$k,.03}$y+=2}
