125
edits
Mozilla2:CAPSSecurity: Difference between revisions
Jump to navigation
Jump to search
removing link-spam
(removing link-spam) |
|||
| Line 108: | Line 108: | ||
If we were to do this at the implementation level, every time C++ called a datasource, they would have to QI that datasource to nsIClassInfo2 and call a method to see whether the rdfIDataSource interface was secured. If it was secured, they would have to set up a security stack. That is a lot more code, and slower, than simply pushing the system principal onto the stack and calling the method (push-pops off the security stack will almost-never involve allocations, and will be blazingly fast). | If we were to do this at the implementation level, every time C++ called a datasource, they would have to QI that datasource to nsIClassInfo2 and call a method to see whether the rdfIDataSource interface was secured. If it was secured, they would have to set up a security stack. That is a lot more code, and slower, than simply pushing the system principal onto the stack and calling the method (push-pops off the security stack will almost-never involve allocations, and will be blazingly fast). | ||
== Todo: Implications for Threading and Event-handling == | == Todo: Implications for Threading and Event-handling == | ||