Maybe JIT is why I can duplicate this on my PHP I don't know why wouldn't have this option on. Anyway I didn't get a 414 from the curl in MOB applied to my test.php
I really shouldn't reply to this troll bait but I don't even get what you are implying. That I don't know anything about PHP, COBAL, Python or Ruby. Which one?????
Oh and yes you are right I don't now anything about COBAL and very little about Python and I think I'll keep it that way.
So it is totally pointless for Java, or for that matter PHP, to protect against buffer overflows in the language? I didn't say that nor do I think it. I think that no language should not be used as a crutch for improper security and that assuming your language is take care of security is not really the best practice.
Especially when PHP's biggest market is inexperienced programmers So the real problem here is inexperienced programmers not the language, which btw I would not encourage for inexperienced programmers.
OK I'll give you there are some problems with the language but nothing in MOB has yet been something that PHP 5 hasn't addressed, or good programming could take care of.
mysql functions which are just imported straight from C. No other language is so crazy as to do that. Most of the functions are imported straight from C. That's how the language started as a big C wrapper that made a web page easier then doing CGI with just C. Again not for the faint of heart even though it's marketed as such.
Because it is painfully obvious that you have no idea what you are doing, and thanks to PHP's lack of secuirty measures against inexperienced programmers, you are very likely creating tons of highly vulnerable programs. Or it could be due to an existing code base. I for one do not wish to randomly hire new programmers and convert over 50000 lines of code. Just like I'm sure my bank is going to go ahead and convert all it's COBAL code to Ruby or Python one of these days.
Other languages tend to have much more secure APIs, letting you get away with not paying as much attention to security. Do yourself a favour and switch to one of them. Right because not paying attention to security is what every programmer should do. Language doesn't make a secure program the programmer does.
Not entirely true JSON extension does give you a javascript object and is very easy to use. But to the defense of the other languages most have plugin/modules/frameworks that take care of this as well.
Correct me if I'm wrong. By my math with APC and assuming a worse case situation of only 2 times acceleration. This means that PHP should execute in 60% the time of Java
I'm not trying to say that's not an bug but...
The exploit requires the PHP code to recursively traverse the array. The request it self does not cause the crash. This can actually be prevent with good PHP code.
So it's possible to not be effected by that bug. Granted even with good PHP code the request takes a long time to handle.
Your Wikis were already broken PHP 4 just lets them work. Or I should say the Wiki's are poorly coded which is why the upgrade didn't take.
Kind of like saying IE 7 breaks a web page when in fact the broken HTML is the problem.
Just like Cario right. Release a product and when people start complaining start talking about the greatest new thing. This keeps would be switchers from switching. MS has been doing this for 10 years now.
Yes history always repeats.
Slashdot Mirror
Maybe JIT is why I can duplicate this on my PHP I don't know why wouldn't have this option on. Anyway I didn't get a 414 from the curl in MOB applied to my test.php
I really shouldn't reply to this troll bait but I don't even get what you are implying. That I don't know anything about PHP, COBAL, Python or Ruby. Which one????? Oh and yes you are right I don't now anything about COBAL and very little about Python and I think I'll keep it that way.
Not entirely true JSON extension does give you a javascript object and is very easy to use. But to the defense of the other languages most have plugin/modules/frameworks that take care of this as well.
Correct me if I'm wrong. By my math with APC and assuming a worse case situation of only 2 times acceleration. This means that PHP should execute in 60% the time of Java
I'm not trying to say that's not an bug but... The exploit requires the PHP code to recursively traverse the array. The request it self does not cause the crash. This can actually be prevent with good PHP code. So it's possible to not be effected by that bug. Granted even with good PHP code the request takes a long time to handle.
Your Wikis were already broken PHP 4 just lets them work. Or I should say the Wiki's are poorly coded which is why the upgrade didn't take. Kind of like saying IE 7 breaks a web page when in fact the broken HTML is the problem.
Just like Cario right. Release a product and when people start complaining start talking about the greatest new thing. This keeps would be switchers from switching. MS has been doing this for 10 years now. Yes history always repeats.