cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Adept /Epic use of PC memory

Highlighted

Re: Adept /Epic use of PC memory


Thanks for the explanation Paul.

Larry Porter
Underwriters Laboratories, Inc.
333 Pfingsten Road
Northbrook, IL 60062

Direct Line: 847-664-3966
Cell Phone: 847-875-2771
Tags (2)
3 REPLIES 3
Highlighted

Adept /Epic use of PC memory

I have a question I hope there is an easy answer to.

I store the DTDs, FOSIs and ACL files for my SGML files on a LAN drive that
the users around the country can access when opening up Adept (we are still
on Adept 8.1) locally on their PC.

When Adept opens the SGML file, are the DTD files, FOSIs ACL etc... placed
in memory on the local PC, or does it still access the stored files on the
LAN for doing functions like presenting the correct list of elements in the
drop down menus and for running the parser to make sure things stay valid
while cut/copy and paste?

Thanks.

Larry Porter
Underwriters Laboratories, Inc.
333 Pfingsten Road
Northbrook, IL 60062

Direct Line: 847-664-3966
Cell Phone: 847-875-2771
Fax: 847-313-3966
E-Mail: lawrence.porter@us.ul.com
Web Site: http://www.ul.com

"Working For a Safer World"

********* Internet E-mail Confidentiality Disclaimer **********

This e-mail message may contain privileged or confidential
information. If you are not the intended recipient, you may not
disclose, use, disseminate, distribute, copy or rely upon this
message or attachment in any way. If you received this e-mail
message in error, please return by forwarding the message and
its attachments to the sender.

Underwriters Laboratories Inc. and its affiliates do
not accept liability for any errors, omissions, corruption
or virus in the contents of this message or any attachments that
arise as a result of e-mail transmission.
*****************************************************************


Highlighted

Re: Adept /Epic use of PC memory

Larry,

When Adept or Epic is launched on your LAN, the product software
is loaded into the client's memory.

When an SGML/XML file is loaded, the associated DTD (actually, the
compiled doctype files) are loaded into the client's memory. The
FOSI is also loaded into memory. When the document is closed
(without ending the session) the doctype/FOSI memory associated
with the doctype of the closed document is freed up.

DTD-based GUIs like the Insert Markup panel use the in-memory
doctype, they do not read files.

Some ACL is loaded into memory at the start of the session, other
ACL is not loaded until it is first needed. In any case, once
loaded, ACL definitions stay in memory for the remainder of the
Adept/Epic session--the associated files are not read again
(unless an application is deliberately written that way).

catalog files and the startup.cf file are checked from the file
system every time Adept/Epic needs them--that is, they are not
read just once, but are read again every time they are needed.
I'm pretty sure this is also true of XSL stylesheets.

Highlighted

Re: Adept /Epic use of PC memory

Let me make one correction to what Paul Klock said. In version 4.2
and above of Epic, XSL stylesheets are loaded into an in-memory cache
and not read again. There is code to check creation dates on the
stylesheets but it only checks the parent. So if a child XSL
stylesheet is changed while a session of Editor or E3 is running, Epic
won't notice. There is an ACL command for clearing the cache if you
may be in this situation and need to ensure that the most recent
stylesheets are used. By child XSL stylesheet, I mean a stylesheet
referenced by xsl:import or xsl:include from a parent XSL stylesheet.

John Dreystadt
Director of Product Management
Arbortext
Announcements