<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.E-MailFormatvorlage22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Setting TMPDIR to „none“ or to „C:\TEMP“ in xep.xml makes no difference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">My media server is called 3 times.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Fritz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>Von:</b> Xep-support <xep-support-bounces@renderx.com> <b>
Im Auftrag von </b>Kevin Brown<br>
<b>Gesendet:</b> Mittwoch, 5. August 2020 21:33<br>
<b>An:</b> 'RenderX Community Support List' <xep-support@renderx.com><br>
<b>Betreff:</b> [xep-support] Re: How often does XEP.BAT use my graphic-URL?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Also note:<br>
<br>
> Are there any reasons why the rendering process doesnt use the TMPDIR for caching purposes?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">What is TMPDIR set to in your xep.xml?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Kevin<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Xep-support <<a href="mailto:xep-support-bounces@renderx.com">xep-support-bounces@renderx.com</a>>
<b>On Behalf Of </b>Vladyslav Sivyakov<br>
<b>Sent:</b> Wednesday, August 5, 2020 12:27 PM<br>
<b>To:</b> <a href="mailto:xep-support@renderx.com">xep-support@renderx.com</a><br>
<b>Subject:</b> [xep-support] Re: How often does XEP.BAT use my graphic-URL?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US">Hello Fritz,<o:p></o:p></span></p>
<p><span lang="EN-US">Your media server controls the expiration policy of your media files. The HTTP "Expires:" header is in charge of telling the HTTP client when the file is to be re-requested.<o:p></o:p></span></p>
<p><span lang="EN-US">I've failed check it myself because mrq12.it2media.de:8081 may not be accessible from the outside, but could it be that the HTTP server returns a bogus "Expires:" header (e.g. if it has a wrongly set system clock) or does not return it
at all?<o:p></o:p></span></p>
<p><span lang="EN-US">To verify, please simply call the following and see the console output:<o:p></o:p></span></p>
<p><span lang="EN-US">curl -D - <a href="http://mrq12.it2media.de:8081/mr/v01/~~~200/mediafile/id/41511906/filetype/pdf?mimetype=true">
http://mrq12.it2media.de:8081/mr/v01/~~~200/mediafile/id/41511906/filetype/pdf?mimetype=true</a><o:p></o:p></span></p>
<pre><span lang="EN-US">Best regards,<o:p></o:p></span></pre>
<pre><span lang="EN-US">Vladyslav Y. Sivyakov, RenderX.<o:p></o:p></span></pre>
<div>
<p class="MsoNormal"><span lang="EN-US">On 03.08.2020 10:19, Kirch Fritz wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Hello Vladyslav,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">thank you for your quick answer, but let us concentrate on the small example fo-file!
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">It has only 1 external-graphic.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I can understand, that throughout the formatting process, XEP has to retrieve various information about the external resource.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">But referring to my small example, why does this retrieval process read the one and only graphic file 3 times?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Are there any reasons why the rendering process doesnt use the TMPDIR for caching purposes?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please apologize my perseverance in getting an answer, but my media server is called 100.000 times a day for providing graphic files.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If there is a small chance to reduce the number of calls, I will be happy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Fritz<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">Von:</span></b><span lang="EN-US"> Xep-support
<a href="mailto:xep-support-bounces@renderx.com"><xep-support-bounces@renderx.com></a>
<b>Im Auftrag von </b>Vladyslav Sivyakov<br>
<b>Gesendet:</b> Freitag, 31. Juli 2020 21:02<br>
<b>An:</b> <a href="mailto:xep-support@renderx.com">xep-support@renderx.com</a><br>
<b>Betreff:</b> [xep-support] Re: How often does XEP.BAT use my graphic-URL?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">Hello Fritz,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">Throughout the formatting process, XEP retrieves various information about the external resources, like dimensions.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">Caching the entire content is problematic because in large documents, the total size of external resources would make the Java environment on a formatting machine quickly run out of memory.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">There is a standard solution for that -- XML Catalogs. You make a local copy of frequently-used resources and configure a Catalog Resolver do the job. Simple ones simply return local files (file:) instead of those
located on remote (http:) computers, but nothing prevents from implementing your own sophisticated one that has some timed-cache strategy and periodically refreshed entities.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">A typical usage is when you're developing DocBook documents, and each rendering process takes an http hit to docbook.sourceforge.net. Of course, this makes rendering slow, and you may want to improve it. Here's
more details:</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="http://www.renderx.com/reference.html#URI_Resolution"><span style="font-size:13.5pt">http://www.renderx.com/reference.html#URI_Resolution</span></a><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="http://www.renderx.com/reference.html#using_catalogs_for_docbook"><span style="font-size:13.5pt">http://www.renderx.com/reference.html#using_catalogs_for_docbook</span></a><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="https://www.oasis-open.org/committees/entity/spec-2001-08-06.html"><span style="font-size:13.5pt">https://www.oasis-open.org/committees/entity/spec-2001-08-06.html</span></a><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:13.5pt">Alternatively, a caching proxy could be a solution, but it may be an overhead and depend on your needs.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"> <o:p></o:p></span></p>
<pre><span lang="EN-US">Best regards,<o:p></o:p></span></pre>
<pre><span lang="EN-US">Vladyslav Y. Sivyakov, RenderX.<o:p></o:p></span></pre>
<div>
<p class="MsoNormal"><span lang="EN-US">On 31.07.2020 09:44, Kirch Fritz wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Hi RenderX-Support Team, hi Kevin<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">in my FO-file (see below and in appendix) you can find excatly one call of <fo:external-graphic> with a url to my graphic file.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">When I use XEP.BAT to render FO into XEPOUT intermediate format, my server protocoll told me, that there are 3 calls fetching the pdf-graphic from my server.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I am wondering, why there are 3 calls?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">With the processing instruction xep-out-embed-images:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> FO -> XEP calls my media server 3 times and XEP -> PDF calls my media server 0 times<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Without the processing instruction xep-out-embed-images:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> FO -> XEP calls my media server 2 times and XEP -> PDF calls my media server 4 times<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">How can I minimize the number of calls to my media server?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Fritz Kirch<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">IT2media GmbH & Co KG<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Nuremberg, Germany<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<pre><span lang="EN-US">_______________________________________________<o:p></o:p></span></pre>
<pre><span lang="EN-US">(*) To unsubscribe, please visit <a href="http://lists.renderx.com/mailman/options/xep-support">http://lists.renderx.com/mailman/options/xep-support</a><o:p></o:p></span></pre>
<pre><span lang="EN-US">(*) By using the Service, you expressly agree to these Terms of Service <a href="http://w">http://w</a><o:p></o:p></span></pre>
<pre><span lang="EN-US">ww.renderx.com/terms-of-service.html<o:p></o:p></span></pre>
</blockquote>
</div>
</body>
</html>