On 7/6/07, Thilo Goetz (JIRA) <[email protected]> wrote:
The character data method of keeping string data in the CAS is obsolete. I'll see if there are any real dependencies on it, or if we can completely remove that code.
Well, almost obsolete. The JNI interface to C++ analytics and the blob serialization method both use the string heap for transfer. In those cases the CAS is delivered [or delivered back] to a Java CAS with strings in the old character array string heap. Also, there is a low-level CAS API that still creates string features in the old string heap. Perhaps Greg is using a C++ analytic? One very easy optimization would be to cache the SofaDataString in the CAS so it would only be created once from the string heap. This would limit the damage to two copies. Eddie
