From: Tobias Burnus <burnus@gmx.de>
Subject: Re: new stuff for brave users
Date: Wed, 04 Aug 2004 14:24:25 +0200 [thread overview]
Message-ID: <4110D579.1030609@gmx.de> (raw)
In-Reply-To: <1861285002.20040804133425@klankschap.nl>
Hello,
Floris van Manen wrote:
>i would opt for a better 'result-ready' flag (e.g. providing the link
>to the result) instead of opening a log file that is of not too much
>interest when everything went OK.
>
>
How about something like that:
Show an intermediate page with a reload HTTP header which calls itself
repeatedly
a) If the PDF file exists redirect to the PDF page
b) If no PDF exists but the texexec has ended, redirect to the logfile
Maybe some option "[ ] don't load PDF file automatically", which shows a
page where I can choose between PDF file and logfile, might be useful too.
The redirect should not use http-equiv but the real HTTP header.
Instead of reloading, you may also try Serverpush:
# Use server push to display a "Please wait..." message for the user while
# executing their query if their browser supports it and they are viewing
# the bug list as HTML and they have not disabled it by adding &serverpush=0
# to the URL.
#
# Server push is a Netscape 3+ hack incompatible with MSIE, Lynx, and
others.
# Even Communicator 4.51 has bugs with it, especially during page reload.
# http://www.browsercaps.org used as source of compatible browsers.
#
my $serverpush =
$format->{'extension'} eq "html"
&& exists $ENV{'HTTP_USER_AGENT'}
&& $ENV{'HTTP_USER_AGENT'} =~ /Mozilla.[3-9]/
&& $ENV{'HTTP_USER_AGENT'} !~ /[Cc]ompatible/
&& $ENV{'HTTP_USER_AGENT'} !~ /WebKit/
&& !defined($::FORM{'serverpush'})
|| $::FORM{'serverpush'};
if ($serverpush) {
print $cgi->multipart_start();
# Generate and return the UI (HTML page) from the appropriate template.
$template->process("list/server-push.html.tmpl", $vars)
print $cgi->multipart_end();
print $cgi->multipart_start(-type=>$contenttype);
}
#Generate normal content
print $cgi->multipart_final() if $serverpush;
Tobias
next prev parent reply other threads:[~2004-08-04 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 9:01 Patrick Gundlach
2004-08-04 9:31 ` Patrick Gundlach
2004-08-04 9:55 ` Vit Zyka
2004-08-04 10:03 ` Patrick Gundlach
2004-08-04 10:42 ` Vit Zyka
2004-08-04 10:06 ` Hans Hagen
2004-08-04 10:12 ` Taco Hoekwater
2004-08-04 10:21 ` texshow-web Patrick Gundlach
2004-08-04 10:57 ` Re: new stuff for brave users Hans Hagen
2004-08-04 11:06 ` Patrick Gundlach
2004-08-04 10:13 ` Mojca Miklavec
2004-08-04 11:17 ` Patrick Gundlach
2004-09-10 9:16 ` Patrick Gundlach
2004-08-04 11:34 ` Floris van Manen
2004-08-04 12:24 ` Tobias Burnus [this message]
2004-08-26 9:43 ` Patrick Gundlach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4110D579.1030609@gmx.de \
--to=burnus@gmx.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).