Title: Message Title
|
|
The general idea here is a good one. We need to find a way to reference the identifiers which *were* associated with an object when a deletion event occurs. However, the existing implementation (PR #537) may need some more thorough testing. I'm worried that looking up the identifiers for *every single event* in the entire system has the potential to cause performance problems. This concern is unproven and speculative as of yet. But, it just seems like it'd be potentially problematic if looking up the identifier in a single IdentifierProvider was expensive (timewise or performance-wise).
|
|
|
|
|
|
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel