RE: [PHP] Re: Accessing data posted from a different URL
[snip] Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. [/snip] That's cool. As far as web development is concerned there are no 'standards', only 'recommendations'. If we had standards we would have fewer problems with differences between browsers. I agree, but no one is laying standards on M$ -- they do whatever the hell they want -- and that's one of the reasons there are so many differences between browsers, especially theirs. I understand why IE6 has about 60 percent of the users, but FireFox is gaining fast at 25 percent last month which beats out everything else except IE6. tedd -- http://sperling.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] [snip] Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. [/snip] That's cool. As far as web development is concerned there are no 'standards', only 'recommendations'. If we had standards we would have fewer problems with differences between browsers. I agree, but no one is laying standards on M$ -- they do whatever the hell they want -- and that's one of the reasons there are so many differences between browsers, especially theirs. I understand why IE6 has about 60 percent of the users, but FireFox is gaining fast at 25 percent last month which beats out everything else except IE6. [/snip] If there were standards each of the browser makers would adhere to them and then add their 'features' on top of those standards. Non-compliant browsers would be left in the dust. I remember a time when Netscape was the leading browser. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
I agree, but no one is laying standards on M$ -- they do whatever the hell they want -- and that's one of the reasons there are so many differences between browsers, especially theirs. I understand why IE6 has about 60 percent of the users, but FireFox is gaining fast at 25 percent last month which beats out everything else except IE6. [/snip] If there were standards each of the browser makers would adhere to them and then add their 'features' on top of those standards. Non-compliant browsers would be left in the dust. I remember a time when Netscape was the leading browser. Yeah, and I still have the 3.5 inch disks of other browsers that preceded Netscape -- but, that's not the point. The point is that M$ will not bow down to w3c, or any other standard set, unless it's proved to them it's in their best interest to do so. As is it now, they still can rain on any standard's parade and do whatever they want. Just take a look at how they handle Unicode in URLs in IE7. As for browsers being left in the dust, web designers still have to design for even outdated browsers to get the greatest number of visitors -- and that fact will be around for a long time. Keep in mind that the rest of the world is tuning into the net via equipment and software that may not be the newest and best. So, if you want that market, then you have to consider their environment. tedd -- http://sperling.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] Yeah, and I still have the 3.5 inch disks of other browsers that preceded Netscape -- but, that's not the point. The point is that M$ will not bow down to w3c, or any other standard set, unless it's proved to them it's in their best interest to do so. As is it now, they still can rain on any standard's parade and do whatever they want. Just take a look at how they handle Unicode in URLs in IE7. As for browsers being left in the dust, web designers still have to design for even outdated browsers to get the greatest number of visitors -- and that fact will be around for a long time. Keep in mind that the rest of the world is tuning into the net via equipment and software that may not be the newest and best. So, if you want that market, then you have to consider their environment. [/snip] That is where the boat was missed at the beginning, there were never standards and had there been (prior to M$ acknowledging that the internet would be a 'big thing') things would be quite different. C'est la' vie -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Manuel Lemos wrote: Some people insist on making everything XHTML compliant just they assume that otherwise it would not be Web standards compliant. That is a silly claim that only leads to all sorts of problems. That assertion is 100% untrue. First of all, XHTML is an excellent idea. Having been based in XML (which is easier to parse than SGML - the markup base for HTML), XHTML is a much, much more interoperable standard. Second of all, the spec has made a number of clarifications which should result in more cross-browser predictability. For instance, if you use method=post because XHTML specification says everything should be in lower case, you will have problems with some browsers and e-mail programs that only accept POST in upper case and fallback to GET when they find something else. Oh, for God's sake, stop selling snake oil. I'm willing to bet $100 that you haven't even read the specification and are inventing crap as you go. For the record, the specification does not say that attribute values need to be lowercase, only attribute *names*. You can put PoST or pOST if you feel like it, and the markup validation status will not change a bit. Also, keep in mind that you can't use Javascript in HTML e-mail messages. That's evidently true, I cannot argue with that. These may not be your actual problems, but at least you have something to start checking. The original poster's problem may be related to the fact that, perhaps, he's checking for the value of a button in the POST variable, when it's a very well known fact that the browser only sends the value of the button if the user *clicks* the button, but not if the user hits ENTER in one of the form fields. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] Some people insist on making everything XHTML compliant just they assume that otherwise it would not be Web standards compliant. That is a silly claim that only leads to all sorts of problems. That assertion is 100% untrue. First of all, XHTML is an excellent idea. Having been based in XML (which is easier to parse than SGML - the markup base for HTML), XHTML is a much, much more interoperable standard. Second of all, the spec has made a number of clarifications which should result in more cross-browser predictability. [/snip] All of these, XML, HTML, XHTML are subsets of SGML. [snip] For instance, if you use method=post because XHTML specification says everything should be in lower case, you will have problems with some browsers and e-mail programs that only accept POST in upper case and fallback to GET when they find something else. Oh, for God's sake, stop selling snake oil. I'm willing to bet $100 that you haven't even read the specification and are inventing crap as you go. [/snip] Easy there sport, no need to fling words like 'crap' around and make assertions about posters, especially when you do not know them. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Jay Blanchard wrote: All of these, XML, HTML, XHTML are subsets of SGML. Your point being? Because my point is centered around the simple fact that XML is easier to parse than generic SGML. XML and SGML aren't fully compatible, if you really want to spot on the differences. XML is stricter, meaning there are fewer possible character representations of the same document, which eases parseability and machine-to-machine interoperability. Easy there sport, no need to fling words like 'crap' around and make assertions about posters, especially when you do not know them. Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. [/snip] That's cool. As far as web development is concerned there are no 'standards', only 'recommendations'. If we had standards we would have fewer problems with differences between browsers. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Manuel Amador (Rudd-O) wrote: snip Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. Jay didn't touch your 'soft spot' (I never knew that about you Jay). Jay was responding to your flame of another poster (Manuel). -- John C. Nichel IV Programmer/System Admin (ÜberGeek) Dot Com Holdings of Buffalo 716.856.9675 [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Jay Blanchard wrote: [snip] Okay, I'm sorry. Dude, you touched a soft spot. It's important, to me, that people respect standards. The wealth of information and communication possibilities that exist today is, in no small part, fueled by the adoption of international standards. [/snip] That's cool. As far as web development is concerned there are no 'standards', only 'recommendations'. If we had standards we would have fewer problems with differences between browsers. Sometimes I wish we did have mandatory standards. Punishable by hanging nonconforming implementations implementors' by their thumbs. :-) But then I close Internet Explorer, and I suddenly feel well again. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] Jay didn't touch your 'soft spot' (I never knew that about you Jay). Jay was responding to your flame of another poster (Manuel). [/snip] True dat, but I have touched.um.er been in touch with my feminine side. I am comfortable with who I am, or something like that. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Hello, on 03/20/2006 07:16 PM Manuel Amador (Rudd-O) said the following: Some people insist on making everything XHTML compliant just they assume that otherwise it would not be Web standards compliant. That is a silly claim that only leads to all sorts of problems. That assertion is 100% untrue. First of all, XHTML is an excellent idea. Having been based in XML (which is easier to parse than SGML - the markup base for HTML), XHTML is a much, much more interoperable standard. Second of all, the spec has made a number of clarifications which should result in more cross-browser predictability. That has nothing to do with what I said. Read again. For instance, if you use method=post because XHTML specification says everything should be in lower case, you will have problems with some browsers and e-mail programs that only accept POST in upper case and fallback to GET when they find something else. Oh, for God's sake, stop selling snake oil. I'm willing to bet $100 that you haven't even read the specification and are inventing crap as you go. Put that gun down. I am not interested in flame wars. If you do not know how to discuss something that you disagree in a civilized manner without departing to personal insult, sorry I can not justify giving you any further attention. For the record, the specification does not say that attribute values need to be lowercase, only attribute *names*. You can put PoST or pOST if you feel like it, and the markup validation status will not change a bit. That is not what the W3C validator thinks. Try entering the following HTML in the W3C markup validator page and see for yourself why people are using post in lowercase because they think being XHTML compliant is a good thing. http://validator.w3.org/#validate-by-input !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; head titleNever mind/title /head body form method=POST action= /form /body /html -- Regards, Manuel Lemos Metastorage - Data object relational mapping layer generator http://www.metastorage.net/ PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Re: Accessing data posted from a different URL
[snip] Sometimes I wish we did have mandatory standards. Punishable by hanging nonconforming implementations implementors' by their thumbs. :-) But then I close Internet Explorer, and I suddenly feel well again. [/snip] It would make life for web developers a lot easier. BTW [Amador] XML and SGML aren't fully compatible, if you really want to spot on the differences. [/Amador] Here is a more complete exploration of the subject, since we have strayed so far off-course. http://www.w3.org/TR/NOTE-sgml-xml.html -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Manuel Lemos wrote: That is not what the W3C validator thinks. Try entering the following HTML in the W3C markup validator page and see for yourself why people are using post in lowercase because they think being XHTML compliant is a good thing. The validator said: value of attribute method cannot be POST; must be one of get, post. so it means you're right. Perhaps the companion DTD to the standard demands either get or post. Would you like to elaborate on which browsers have trouble interpreting lowercase actions in form tags? http://validator.w3.org/#validate-by-input !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; head titleNever mind/title /head body form method=POST action= /form /body /html -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
On Mon, March 20, 2006 4:16 pm, Manuel Amador (Rudd-O) wrote: The original poster's problem may be related to the fact that, perhaps, he's checking for the value of a button in the POST variable, when it's a very well known fact that the browser only sends the value of the button if the user *clicks* the button, but not if the user hits ENTER in one of the form fields. That's actually browser-dependent behaviour... I think it was Netscape that sent the name/value just as if the user clicked the button, but IE that didn't. Or maybe vice-versa. There is something to be said for not trying to make your code XHTML compliant, though... I'm more worried about works in all browsers compliant, which, unfortunately, is not a documented standard anywhere. :-v -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Accessing data posted from a different URL
Hello, on 03/20/2006 07:52 PM Manuel Amador (Rudd-O) said the following: That is not what the W3C validator thinks. Try entering the following HTML in the W3C markup validator page and see for yourself why people are using post in lowercase because they think being XHTML compliant is a good thing. The validator said: value of attribute method cannot be POST; must be one of get, post. so it means you're right. Perhaps the companion DTD to the standard demands either get or post. Would you like to elaborate on which browsers have trouble interpreting lowercase actions in form tags? I do not recall, but I think there was a problem with some Opera versions. -- Regards, Manuel Lemos Metastorage - Data object relational mapping layer generator http://www.metastorage.net/ PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
