Thinking about this a bit more, I've come round to the position that I don't see why database record IDs are a problem in this context. All we need to do is to inform people that we explicitly deny long-term meaning to these identifiers; they should be assumed to have session scope. If you store one and expect it to refer to the same object after your program exits, you are breaking the rules and may get the confusion that you deserve.
If you happen to notice that they seem to correspond to database record IDs, that is not a guarantee that they will continue to do so. If you happen to notice that they seem to persist for months or years, that is not a guarantee that they won't be different tomorrow. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
