Hi Nathan and Scott,

Thank you for responding, I will be trying the NFS route.


The proxy is running in apache on the 400, and is our main web server. As to why the pdf's aren't hosted on the 400? They initially were, but now there are roughly 900,000 of them, they took up too much space, so we moved them to a cheaper storage box. One reason for the performance hit, is that the pdfs are grouped (think separate directories) and when a visitor searches for pdfs, I first verify that the pdf exists (to avoid dead links) before writing the link for it to the screen.

Up to now, I have been using GETURL to check the existence of pdfs, but I suspect I can improve performance, by cutting out the web layer, configuring NFS and using CHKIFSOBJ to verify files.

Thanks,
Jeff




From: Nathan Andelin To:Web Enabling the AS400 / iSeries Date: 11/2/2010 8:54 PMSubject: Re: [WEB400] Webserving pdfs via reverse proxy, QNTC, NFS> From: Scott Klement
Is there a reason you're using a proxy/nfs/qntc in the first place?


Good question. QNTC indicates that an IBM i application is accessing stream
files located on a Windows server. But why? On which machine/OS is the reverse
proxy running, and why? Windows or IBM i? If static PDF files are stored in a
Windows directory, then why not run the reverse proxy on the Windows server, so
it can access the local file system? Then only forward requests to IBM i to
serve dynamic content?

This could get convoluted if you were running a reverse proxy under IBM i, along
with a normal HTTP server instance, where one or more HTTP server instances were
serving from the QNTC file system - which points to Windows.

-Nathan





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.