Hi Martin,
I thought the complete day about how to implement your idea but then somebody comes up with question, what happens if the last admin from a multi approval scenario find an error in the first object but wants to sign the other n-1 objects?
The next question (from me) was how should an operator on a web frontend safely sign several requests? I think he would simply lose the overview. I only know one situation where several objects must be signed and this is the batch system but this system can already do this by signing every request (one-by-one). So is a method for grouped signing really required?
The next question is the signing itself. Would it be a good idea to create a table for approved actions which includes action, object_type, object_id, user and method (plus data and format)? This would allow 4-eyes-principle and other things without singing. Signing could be still added by an own table which references to the action (and not to the object itself). The table is a first idea how to implement your approval handle (but more generalized).
Michael -- _______________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
