Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
What is the reason for temporary objects
Yurie_Nagorny_(ynagorny_-_(deleted))
I noticed that many objects have a child object which a name like #. As I understand, those are so called temporary objects.Also, I noticed that some objects don't have any temporary objects. And also there are some objects with more than one temporary object.Can someone shed some light on what these temporary objects are and what their purpose is?Thank you,Yurie
Find more posts tagged with
Comments
Hans Stoop
Message from Hans Stoop via eLinkWell, that is a very good question. One of the primary advantages isthat temp objects are never saved back into you Ospace file. So,whatever you do to a temp object, it wouldn't influence the status ofyour Ospace.For the temp objects that are created on the fly (unlike the temp objectthat are created at start-up) you are sure that all the features are asthey should be and don't have values left over from previous requests.Temp objects can be seen as instances of classes.Hans----------------------------------------------------------------------- Open Text - The market leader in Enterprise Content Management.-----------------------------------------------------------------------Hans StoopSenior Consultant, Business Unit EMEA SolutionsOpen Text CorporationPhone: +31 (0)23 565 2333Fax: +31 (0)23 555 3410GSM: +32 (0)485 160 258________________________________This e-mail is protected by domestic and international copyright lawsand treaties and is the property of Open Text Corporation, it maycontain confidential and/or trade secret information of the Open TextCorporation and/or its subsidiaries (OTC), and may be subject to legalprivilege in favor of OTC. This e-mail may only be lawfully received,accessed, displayed on a computer screen, printed, copied, and/or usedby the specific addressee(s) named above ("Authorized Recipient") forthe purpose for which it was sent by OTC. All other rights and licensesto this e-mail are fully reserved to OTC. If you are not an AuthorizedRecipient, you are required to immediately delete this e-mail in itsentirety without printing, copying, using, and/or re-transmitting thise-mail, either in whole or in part. The transmission of this e-mail byOTC is not to be construed as a waiver by OTC and/or the individualsending this e-mail on behalf of OTC of any of their respective rightsor privileges at law or otherwise, howsoever arising. > -----Original Message-----> From: eLink Discussion: Development Discussion > [mailto:development@elinkkc.opentext.com] > Sent: donderdag 19 oktober 2006 20:30> To: eLink Recipient> Subject: What is the reason for temporary objects> > What is the reason for temporary objects Posted by Nagorny, > Yurie on 10/19/2006 02:25 PM> > I noticed that many objects have a child object which a name > like #. As I understand, those are so called > temporary objects.> > Also, I noticed that some objects don't have any temporary > objects. And also there are some objects with more than one > temporary object.> > Can someone shed some light on what these temporary objects > are and what their purpose is?> > Thank you,> Yurie> > [To reply to this thread, use your normal E-mail reply function.]> > ============================================================> > Discussion: Development Discussion>
https://knowledge.opentext.com/knowledge/llisapi.dll/open/786303>
; > Livelink Server:>
https://knowledge.opentext.com/knowledge/llisapi.dll>
; > To Unsubscribe from this Discussion, send an e-mail to > unsubscribe.development@elinkkc.opentext.com.> > >
Howard_Pell
Temporary objects are the equivalent of a process on a multi-user/multi-tasking operating system. Recall from your first-year Operating System course that each user must have their own copy of the s/w as well as their data, so each user cannot modify the data of another user.When a request handler is called (for example) it could be called by many users concurrently (simultaneously on multiple CPU machines). I want to use the ll RH to add a document and you want to use the ll RH to add a document. By giving us each our own temporary object, there is no collision of data, nor is there any waiting as there would be if there was only one ll RH to share.I hope this helpsHoward
Janusz_Frydecki
You may want to take a look here to get more information
http://communities.opentext.com/communities/livelink.exe?func=ll&objId=3037688&objAction=WikiViewAlso
, if you know more about these than what is written in the wiki article, don't forget to update the page!Thanks to all!Louis