From: Jim Dabell (firstname.lastname@example.org)
Date: Sat Sep 07 2002 - 17:37:09 BST
-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 07 September 2002 3:28 pm, Simon Willison wrote:
> At 15:55 07/09/2002 +0000, Jim Dabell wrote:
> >Is an entry with 20 links really that common? Even if it is, surely it
> >would be a much better approach to do this processing *after* you have
> >returned the page to the client (i.e. all you do on the submitting page
> > is schedule an at job for a couple of minutes into the future, or put
> > an entry into the database for a cron job to notice).
> This is more of a problem with PHP than anything else. As far as I know,
> the only way to make PHP return information to the client before it has
> finished processing is to use output buffering and "flush" output
> straight to the client while the script is still going. This is great,
> except I'm pretty sure (not certain mind) that if the user terminates the
> connection by hitting "stop" the PHP script will also terminate, which
> would kill off your pinging process mid flow.
"You can decide whether or not you want a client disconnect to cause your
script to be aborted."
By the way PHP 4.2.3 has been released - without a changelog or any hints as
to what the changes are. Anyone know what's up with that?
> If it turns out a centralised service is required we can set one up later
> - I've got the code for it already.
Yes, it would be a good idea to hang onto it anyway, although personally, I
have the nasty habit of rewriting anything older than a couple of months
even if the code works ;)
Perhaps the centralised approach would be good for when you only want
certain classes of pingbacks (e.g. only Spanish pingbacks)? You could use
the centralised system as a mini-dmoz.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----
Message sent over the Blogite mailing list.
This archive was generated by hypermail 2.1.5 : Sat Sep 07 2002 - 17:05:01 BST