Or learn Python and write a Product for Zope, adding more value to Zope;)...
When it comes down to it, this guy is having a problem with the UNIX permissions structure, so you'd be writing a new permissions module for Apache. Zope already has it's own permissions structure. In Zope, I would create a folder for each user, giving them "Owner" privileges on the that folder, and say that, by default, only Owners (and Managers) can View the content of the folder. This additionally allows users to specify if they'd like Anonymous users to view specific items. Done in 5 minutes. Time for coffee!
If you had Apache feeding the requests to Zope (or any other Content Management System, really), then you could get much finer-grained control on permissions.
If Player 3 always guesses red, then he will be wrong 50% of the time, and since, if one person guesses wrong, the whole team is wrong, this gives a 50% success rate.
from Miscro$oft (re SOAP 1.0):
"SOAP doesn't care what operating system, programming language, or object model is being used on either the server side or the client side: it is utterly agnostic, except that it needs HTTP as a transport." ( emphasis is mine )
and from W3C( re SOAP 1.1):
"SOAP can potentially be used in combination with a variety of other protocols"
Actually, the SOAP spec does not specify which protocol you need to use to pass the messages. HTTP will obviously be a very common choice, but it's OK to use other protocols.
Slashdot Mirror
I think you mean a hundred rolls of film?
This guy seemed to have very little positive to say about anyone/anything except himself and his own "ideas". I got nothing out of that really.
*That's* why 641C was doing that!! That annoyed the hell out of me. You'll be happy to know that it's fixed now.
Or learn Python and write a Product for Zope, adding more value to Zope ;) ...
When it comes down to it, this guy is having a problem with the UNIX permissions structure, so you'd be writing a new permissions module for Apache. Zope already has it's own permissions structure. In Zope, I would create a folder for each user, giving them "Owner" privileges on the that folder, and say that, by default, only Owners (and Managers) can View the content of the folder. This additionally allows users to specify if they'd like Anonymous users to view specific items. Done in 5 minutes. Time for coffee!
If you had Apache feeding the requests to Zope (or any other Content Management System, really), then you could get much finer-grained control on permissions.
I don't think it'll work. chroot's work on processes (right?), and all the HTTP requests are being served by the same (group of) processes.
awwwwww yes ... Fila Brazillla has gotten quite a few bucks from me both b/c of Drone Zone, and MonkeyRadio ... good stuff.
If Player 3 always guesses red, then he will be wrong 50% of the time, and since, if one person guesses wrong, the whole team is wrong, this gives a 50% success rate.
from Miscro$oft (re SOAP 1.0):
"SOAP doesn't care what operating system, programming language, or object model is being used on either the server side or the client side: it is utterly agnostic, except that it needs HTTP as a transport." ( emphasis is mine )
and from W3C( re SOAP 1.1):
"SOAP can potentially be used in combination with a variety of other protocols"
Actually, the SOAP spec does not specify which protocol you need to use to pass the messages. HTTP will obviously be a very common choice, but it's OK to use other protocols.