Hi,
This is not very complicated... It is just a little hard to write down in
a comprehensible way.
The server keeps some things in memory and some not. The definitions are
always stored in the database, and never on the server hard-drive. You
need not concern yourself with how the server stores form definitions at
this point. The thing you need to know is that the server keeps a
modify-timestamp for all objects. When you change a FORM/ACTL/MENU, this
timestamp will be updated.
When a user opens a form, the cache may be read from the client hard-drive
if it exists (arf and arv files).
If the cache does not exist on the client, it will be retrieved from the
server and stored in memory and on the hard-drive. The ARExport-call is
used.
Each cached object FORM/ACTL/MENU has the last known modify-timestamp
attached to it. The ARValidateFormCache() is used to compare this
timestamp to the timestamp the server. If the timestamp is older than the
modify-timestamp of the object on the server, the object will be
reexported using ARExport().
If you open the same form again, without closing the first form-window,
the cache will not be validated. If you close all instances of the form,
and then reopen it, the cache will be revalidated. This, in general, is
how it works. Table-field-forms may also be validated at times I think.
If you are using Mid-Tier, there is other kinds of caching going on on the
web server and the web client. The behavior has changed some over time.
But it seems like you are interested in the native user client here.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Hi LJ,
> In our case as mentioned in the below thread, we have cleared the cache in
> ARHome directory, then can you please tell us how this API
> ARValidateFormCache validate the client cache with the server one?
>
> Regards
> Gopal
>
>
> LJ LongWing (Head) wrote:
>>
>> To the best of my knowledge, yes, validate the cache that's stored in
>> the
>> servers memory
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:[email protected]] On Behalf Of Gopal-srg
>> Sent: Wednesday, March 31, 2010 11:06 AM
>> To: [email protected]
>> Subject: Re: ARValidateFormCache
>>
>> Hi LJ,
>> If the cache is stored in memory, then the API call ARValidateFormCache
>> is
>> refereing the memory cache content?
>>
>> Regards,
>> Gopal
>>
>>
>> LJ LongWing (Head) wrote:
>>>
>>> I believe the cache is stored in memory, not in any place on the disks
>>> of the server.
>>>
>>> -----Original Message-----
>>> From: Action Request System discussion list(ARSList)
>>> [mailto:[email protected]] On Behalf Of Gopal-srg
>>> Sent: Tuesday, March 30, 2010 12:42 PM
>>> To: [email protected]
>>> Subject: ARValidateFormCache
>>>
>>> Hi all,
>>> Need to know some information the ARValidateFormCache API call.Have
>>> gone through the API Programmer's PDF, but it describes only about API
>>> function/Struct definition.
>>>
>>> In our client, even we clear the local file cache(ARHome), when we try
>>> to access an application entry point link(previously application is
>>> opened and closed, after that the cache were cleared and in same login
>>> session) this ARValidateFormCache API has been called.
>>>
>>> We though that this API will be called only when the files are in the
>>> local client cache(ARHome), but this is not the case.
>>>
>>> Is this ARValidateFormCache refereing to any cache made in server? If
>>> so, in server(ARS 7.5 - Linux OS ) were the cache files are stored?
>>>
>>> Please guide us in solving this issue.
>>>
>>> Regards,
>>> Gopal
>>> --
>>> View this message in context:
>>> http://old.nabble.com/ARValidateFormCache-tp28086744p28086744.html
>>> Sent from the ARS (Action Request System) mailing list archive at
>>> Nabble.com.
>>>
>>> ______________________________________________________________________
>>> ______
>>> ___
>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend
>>> wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>>
>>> ______________________________________________________________________
>>> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/ARValidateFormCache-tp28086744p28098924.html
>> Sent from the ARS (Action Request System) mailing list archive at
>> Nabble.com.
>>
>> ____________________________________________________________________________
>> ___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10
>> www.wwrug.com ARSlist: "Where the Answers Are"
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/ARValidateFormCache-tp28086744p28104795.html
> Sent from the ARS (Action Request System) mailing list archive at
> Nabble.com.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
