Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <4077582.NtEabsPJ40@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Thu, 28 Nov 2013 16:39:47 +0100 User-Agent: KNode/4.11.3 Content-Transfer-Encoding: 7Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <529251aa$0$9524$9b4e6d93@newsspool1.arcor-online.net> <52975cc8$0$6565$9b4e6d93@newsspool4.arcor-online.net> MIME-Version: 1.0 Lines: 22 NNTP-Posting-Date: 28 Nov 2013 16:39:48 CET NNTP-Posting-Host: 54f6038d.newsspool4.arcor-online.net X-Trace: DXC=en3WWEol968i6K;>iZ]7634IUK Mel Smith wrote: >> (btw, another option -- which I may have to use- is to build a pdf >> file >> at the server, and then send a link to the client to *that* file. But >> this means I may have to save this file on the server, or maybe email >> file to the client. Both are unpalatable options for me.) > > There is, however, a third option: build the PDF dynamically on each > respective request and deliver it as application/pdf. In your case that > seems to be unnecessarily complicated and wasteful, but there might be > use cases where this technique could be reasonable deployed. It is the best current practice for small PDF documents that have to be up-to-date. -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.