Accessing Data across Livelink kernel threads

To all Oscript wizards:Is there a (supported) way to access data across threads running in a Livelink instance? It should take the form of some type of singleton, accessible across all Livelink thread instances [i.e. a "frame" that is initiated only once across all threads and then referenced]. The current singleton implementation only applies within a kernel thread (not accessible from other threads).Any ideas?Your help would be greatly appreciated!!Thanks,Rolf(rolf@stasolutions.co.za)

Find more posts tagged with

Comments

Andrew_Kane

Message from Andrew Kane via eLinkSome comments from Brian Whitlock:Application globals in general should not be used as KOSValues that arereferences are not thread safe. The opentext.ini cache is shared across all threads.The best way to share data is through the database as you never know ifyou are deployed in a cluster or not.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Monday, March 06, 2006 9:18 AMTo: eLink RecipientSubject: Accessing Data across Livelink kernel threadsAccessing Data across Livelink kernel threadsPosted by Poser, Rolf H on 03/06/2006 09:13 AMTo all Oscript wizards:Is there a (supported) way to access data across threads running in aLivelink instance? It should take the form of some type of singleton, accessible across allLivelink thread instances [i.e. a "frame" that is initiated only onceacross all threads and then referenced]. The current singletonimplementation only applies within a kernel thread (not accessible fromother threads).Any ideas?Your help would be greatly appreciated!!Thanks,Rolf(rolf@stasolutions.co.za)

Rolf_Poser_(eu0018377_-_(deleted))

Brian & Andrew - thanks for the comments!The reason I was interested is to minimise file / db access in order to maximise speed.I've been able to solve my problem another way, but if you think about some of the Open Text modules, a shared in-memory cache could be useful.One example is the memory cache for Virtual Folders - at this stage, each thread builds up its own cache. A shared cache would allow for more memory to be assigned, and would result in better caching and therefore performance.Anyway - I'm happy with my current solution, since I'm not actually caching, but just storing data in a $KERNEL.Singleton for each thread.Regards,Rolf.

Hans Stoop

Message from Hans Stoop via eLinkRolf,the opentext.ini file is stored in cache. Changes you make to it whileLivelink is running are not recognized until after a restart ofLivelink. In case it is actually share among the threads as Brian says,then this could be a solution.Other ini files are also cached. I don't know if they are also sharedbetween threads.Hans> -----Original Message-----> From: eLink Discussion: Development Discussion > [mailto:development@elinkkc.opentext.com] > Sent: donderdag 9 maart 2006 6:32> To: eLink Recipient> Subject: RE Accessing Data across Livelink kernel threads> > RE Accessing Data across Livelink kernel threads Posted by > Poser, Rolf H on 03/09/2006 12:29 AM> > Brian & Andrew - thanks for the comments!> > The reason I was interested is to minimise file / db access > in order to maximise speed.> > I've been able to solve my problem another way, but if you > think about some of the Open Text modules, a shared in-memory > cache could be useful.> > One example is the memory cache for Virtual Folders - at this > stage, each thread builds up its own cache. A shared cache > would allow for more memory to be assigned, and would result > in better caching and therefore performance.> > Anyway - I'm happy with my current solution, since I'm not > actually caching, but just storing data in a > $KERNEL.Singleton for each thread.> > Regards,> Rolf.> > [To reply to this thread, use your normal E-mail reply function.]> > ============================================================> > Topic: Accessing Data across Livelink kernel threads> https://knowledge.opentext.com/knowledge/livelink.exe/open/4732991> > Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/livelink.exe/open/786303> > Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe> > To Unsubscribe from this Discussion, send an e-mail to > unsubscribe.development@elinkkc.opentext.com.> > >