We've found some code that uses ExternalEntry. We'd have to perform a complete audit to determine if it's still actually in use, but we're considering our possible courses of action if we have to replace it. In the documentation for ExternalEntry it indicates that its functionality with regards to id-based queries can be replaced by readByID, etc. and with regards to extended queries can be replaced with SQLQuery; for weak-type entries it recommends using SpaceDocument. There is only one problem with that; in fact ExternalEntry is an overloaded object as it was sometimes used to hold lists of Ids.
The simplest way forward would appear to be use IEntryPacket or one of the other interfaces, but all of these are internal and thus should perhaps not be used with a view to the future. What would you suggest? One of our thoughts is to create a SpaceDocumentEntry class that provides both weak types as well as an internal list of Ids when that type of functionality was required, but there may be other options and we're curious what your thoughts on the matter are.
Thanks
jb.ext
↧