php-general Digest 6 Jun 2011 12:55:43 -0000 Issue 7347
Topics (messages 313405 through 313409):
Re: phpsadness - P.C. shmee seee.
313405 by: Robert Cummings
313407 by: Richard Quadling
313408 by: Robert Cummings
Re: phpsadness - the second tangent...
313406 by: Daevid Vincent
PHP download page blocking other HTTP requests
313409 by: Pete Ford
Administrivia:
To subscribe to the digest, e-mail:
php-general-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-general-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-gene...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
On 11-06-05 07:28 PM, Richard Quadling wrote:
On 5 June 2011 19:15, Robert Cummings<rob...@interjinn.com> wrote:
2 words... progressive enhancement. If your browser doesn't support a
feature then it should degrade gracefully. Accessible web philosophy 101. I
hate going on to some website, especially government, and finding that it
sniffs my browser and then completely excludes me if it doesn't like what it
finds.
There is another approach. Regressive Enhancement.
Essentially, create your site with all the bells and whistles enabled.
Make full use of all / any standards compliant feature.
For browsers not capable of supporting that, use emulation techniques.
Sitepoint have a blog about this technique :
http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/
From my cursory read... regressive enhancement would need to rely on
progressive enhancement to work :) If there's no JavaScript to do the
lifting, then how can you regress?
An interesting read all the same. It's kind of like the compatibility
layer PEAR releases for older versions of PHP so they have access to
newer functions and stuff but implemented in PHP rather than C.
Cheers,
Rob.
--
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.
--- End Message ---
--- Begin Message ---
On 6 June 2011 01:44, Robert Cummings <rob...@interjinn.com> wrote:
> On 11-06-05 07:28 PM, Richard Quadling wrote:
>> There is another approach. Regressive Enhancement.
>>
>> Essentially, create your site with all the bells and whistles enabled.
>> Make full use of all / any standards compliant feature.
>>
>> For browsers not capable of supporting that, use emulation techniques.
>>
>> Sitepoint have a blog about this technique :
>>
>> http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/
>
> From my cursory read... regressive enhancement would need to rely on
> progressive enhancement to work :) If there's no JavaScript to do the
> lifting, then how can you regress?
>
> An interesting read all the same. It's kind of like the compatibility layer
> PEAR releases for older versions of PHP so they have access to newer
> functions and stuff but implemented in PHP rather than C.
>
> Cheers,
> Rob.
If you were to start with a full bells and whistles HTML5/CSS3 site,
then you would already have an issue with very very old and / or non
visual browsers I think.
If they don't have JS, then the level of FOOBAR is going to be even greater.
So. Interesting but maybe useless.
--
Richard Quadling
Twitter : EE : Zend : PHPDoc
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
--- End Message ---
--- Begin Message ---
On 11-06-06 05:18 AM, Richard Quadling wrote:
On 6 June 2011 01:44, Robert Cummings<rob...@interjinn.com> wrote:
On 11-06-05 07:28 PM, Richard Quadling wrote:
There is another approach. Regressive Enhancement.
Essentially, create your site with all the bells and whistles enabled.
Make full use of all / any standards compliant feature.
For browsers not capable of supporting that, use emulation techniques.
Sitepoint have a blog about this technique :
http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/
From my cursory read... regressive enhancement would need to rely on
progressive enhancement to work :) If there's no JavaScript to do the
lifting, then how can you regress?
An interesting read all the same. It's kind of like the compatibility layer
PEAR releases for older versions of PHP so they have access to newer
functions and stuff but implemented in PHP rather than C.
Cheers,
Rob.
If you were to start with a full bells and whistles HTML5/CSS3 site,
then you would already have an issue with very very old and / or non
visual browsers I think.
If they don't have JS, then the level of FOOBAR is going to be even greater.
So. Interesting but maybe useless.
But it's an established fact that websites can be presented without
JavaScript. It may look old-fashioned, but everyone can view it. Even in
Netscape 4 a site can be readable (even if ugly). Exclusively require
JavaScript to view the content and this is no longer the case. That's
the problem with regressive enhancement, it requires feature X to be
enabled to facilitate the regression... which isn't very regressive. If
it can be viewed in lynx then there's a good chance it can be
viewed/read aloud by anything. Yes, you might not be able to view some
HTML 5 canvas application, but there's nothing preventing you from
having a paragraph with a brief description and a link to an image which
is then progressively enhanced to the full blown HTML 5 canvas version.
I think regressive enhancement is a good idea, just that one shouldn't
throw out progressive enhancement when ideally (yes I'm an idealist :)
the two would work best together...
- vanilla website
- progressively enhance
- regressively enhance where feature Y can be implemented given
that feature X exists.
Cheers,
Rob.
--
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.
--- End Message ---
--- Begin Message ---
Really? This thread is going to tangent yet again to something completely
irrelevant?
FWIW, I used some stupid "WinLIKE" JS framework by http://ceiton.com
These bastards haven't updated it since 2007
http://wiki.winlike.net/index.php/Version_History
Normally not a big deal, but they "patented" it (or tried), and it's all
minified and IN GERMAN! So trying to figure out how and where to remove that
browser check has been a futile effort that I just don't care to spend any
more time on.
This is yet another reason and example as to why I HATE frameworks. I should
have never used their crappy one and just built everything myself.
My current PERSONAL site is starting to show its age and is due for a
re-vamp, but honestly I just have too much other work on my plate that pays
me. 90% of the people out there use FF or IE and so I don't really care
about Safari or Opera or the other fringe browsers for my PERSONAL site.
-----Original Message-----
From: Tamara Temple [mailto:tamouse.li...@gmail.com]
Sent: Saturday, June 04, 2011 10:09 PM
To: Daevid Vincent
Cc: php-gene...@lists.php.net
Subject: Re: [PHP] phpsadness - P.C. shmee seee.
On Jun 3, 2011, at 3:52 PM, Daevid Vincent wrote:
> ...actually, I do have some good ones here:
> http://daevid.com/content/examples/procmail.php
"It appears your browser does not support some of the advanced
features this site requires.
Please use Internet Explorer or Firefox."
ROFL. Good one.
--- End Message ---
--- Begin Message ---
I have a file download 'guardian' page which does something like this:
$size = filesize($path);
$fi = @finfo_file($path, FILEINFO_MIME_TYPE);
@header('Content-type: ' . $fi);
@header('Content-Length: ' . $size);
@readfile($path);
exit;
($path is derived from parameters in the request, including checks for nasties
and some access control checks in the system)
When a link is clicked which points to this script, the file is downloaded (well
and good...), but in Firefox (3.x, 4.x at least), it seems to block any further
interaction with the browser until the download is complete - some of the files
are 60Gb and the server is on a 2mbit line, so it can take some time to download.
Is there something on the Apache/PHP end that might be causing this blocking?
(Apache 2.2.10, PHP 5.2.14)
I suspect not, since using Chrome as the browser doesn't appear to have the same
problem, but I wondered whether there was some way that FF was handling the
headers might be causing it.
I can't seem to devise a suitable Google search to get any mention of similar
behaviour so I thought I'd ask some experts :)
--
Peter Ford, Developer phone: 01580 893333 fax: 01580 893399
Justcroft International Ltd. www.justcroft.com
Justcroft House, High Street, Staplehurst, Kent TN12 0AH United Kingdom
Registered in England and Wales: 2297906
Registered office: Stag Gates House, 63/64 The Avenue, Southampton SO17 1XS
--- End Message ---
