From: Shen, G. <sh...@bn...> - 2010-08-11 13:44:12
|
Marty Kraimer wrote: > [...] > > For pvAccess it already has a method that tells it to disconnect from > the record. After this it must NEVER access the record again. > It looks that it is pvAccess' responsibility to prevent a unwanted access to a non-exist record or a record just deleted. Is it true? If yes, should it be moved into pvEngine? > [...] > > pvAccess creates top level PVStructures that are seen by the client. It > should take the responsibility of garbage collection these top level > structures but again the client does not have to get involved. > Is the top level pvStructure created by pvAccess, or by pvEngine? I confused myself. I thought the garbage collection is done by pvEngine. Guobao > The PVStructure interface can have a method named destroy, which when > called, will delete all storage connected with the structure. This will > make garbage collection easy for deleting a record in a pvEngine and for > pvAccess to garbage collect a top level PVStructure. > > Marty > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > > |