Thibaud Morel l'Horset wrote:
> What I did to solve this problem is simply create a few crons on the
> server that each do a mechanize
> (http://wwwsearch.sourceforge.net/mechanize/) http call to a specific
> location in Zope which basically acts as a private API: when called, it
> executes a function that triggers whatever needs to happen. I hard-coded
> a check that the source IP must be the specific internal address of the
> server Zope runs on. That way I know that the functions can't be called
> from the outside.
This is all extremely fragile and generally not a good idea.
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
