Since the original question related to handling 100+ concurrent requests, the service is likely an Internet-facing web site. In that arena, most companies do ditch Windows, even if they're using Exchange, etc. on their internal company servers. A "ditch Windows" answer is simply sharing the prevailing wisdom. If there's some reason why they can't ditch Windows in this situation, they should have said so in the question, since that's the obvious answer to expect.
You can use BRL that way. See the testsuite directory in the source distribution for how to process BRL files without any web framework. Additionally, there's a builtin function for LaTeX-escaping strings, in case you want really nicely formatted PDF reports, as I do. Additionally, when you embed code to generate an email within a file that generates a web page, the same nice template syntax is used as at the top level, unlike any similar technology that I'm aware of.
I have moderator points and could have modded you down, but I'd rather reply.
using VB.NET theres 100% logic/presentation seperation
This, as always, is untrue. There is no such thing as 100% logic/presentation separation. Suppose you have a wide table that is the result of a database query. Should you make every third row a different background color to ease horizontal navigation? Every other row? Just leave them all the same background color? This decision is both a presentation decision and a logic decision. How many decimal places should you show for this particular number? There's another decision where logic and presentation are intertwined. Clearly both the model matters (How many decimal places are necessary for the entity to have meaning?) and the view matters (How much horizontal space do I have on this report?) I could go on and on with examples where you cannot separate the logic from the presentation.
You can partially separate logic and presentation. How much separation is appropriate depends on the project...actually on individual instances within the project of logic/presentation relationships.
There are lots of people out there who do too little separation of presentation and logic. They'll end up with a better end result if they use Velocity, Freemarker or webmacro. There may also be people out there who produce overly bland user interfaces because they try too hard to separate presentation and logic. They would benefit from JSP, BRL, Tea, PHP, CF, or somesuch. Although with BRL it's easier to extricate the logic from the presentation if you start out with too little separation.
OK, enough ranting. It's just that this "100% separation" fiction is one of my pet peeves.
Successful programming projects save companies lots of money. One successful project will only whet their appetite for more. I expect there will always be work for me, no matter how many overseas programmers compete.
Another post seems to indicate this was done via software to automatically detect defects. Many (most?) security defects cannot be detected automatically, as they involve using the software in an unintended way.
YANAL. IANAL. Yet we can still read the court decision to address some of our curiosity. You'll see that the EULA issue is, in fact, important.
Where patent enters into it is the possibility that the US Supreme Court declined to hear the case because it touches on software patents. The latest US Supreme Court case (Diamond v. Diehr, 1981), reaffirmed that software is not patentable. Lower court rulings have boldy contradicted this ruling, and the Supreme Court hasn't been willing to face up to the politically messy issue. Perhaps that's why they declined to hear this case, despite its sweeping implications. See Justice Dyk's dissent for a scary description of those implications.
See, here's another person who thinks stable and unstable are your only Debian choices. See also the earlier posts about stable servers vs less stable desktops. Nobody knows about the Debian testing distribution unless they hear about it from somebody else. Rather than write a long essay about how everybody needs to market Debian better, volunteer time to change Debian's web site to make the testing distribution more prominent. Then watch Debian's reputation change. The Debian testing distribution rocks.
Those new arrays are NOT necessary.
on
PHP 5 Beta 1
·
· Score: 1
Those new arrays are not necessary. They could have changed the language to include a simple declaration of what variables are inputs, like define-input in BRL. This eliminates all the security issues and is nearly as simple.
From my POV, this looks like the most significant change:
Optimizations have been made to the core libraries to reduce startup time. For a small command line application, startup time has been reduced by roughly thirty percent; for a small Swing application, by fifteen to twenty percent.
The latest word from the U.S. Supreme Court is that software patents are invalid (Diamond v. Diehr, 1981). Lower courts have contradicted this ruling since then, and the Supreme Court hasn't heard any relevant cases recently. Maybe if you could get your case up to the Supreme Court they would reinforce their 1981 ruling. Too bad lower courts have managed to make it "illegal" to "infringe" on patents that the country's highest court has ruled invalid.
Functions cannot bind variables. Here are some useful macros from Monday's release of BRL, a Scheme system in some ways similar to PHP.
(define-input a b c...) (define-cookie x y z...) (define-session q r s...) (define-path t u v...)
This would bind the local variable a to the value of an HTML input named "a". Similar with b and c. Similar with cookies, session variables and URL path segments. Try writing those as functions.
Ignore what the other poster said about converting dvi. Use pdflatex to go straight from latex source to pdf. The supertabular package matches so perfectly what you asked for in your first post, that I thought you might be trolling for a pdflatex answer.
MySQL is not easier than PostgreSQL
on
PHP Cookbook
·
· Score: 1
I've used both MySQL and PostgreSQL. In my experience MySQL is not easier.
You should make sure your app is accessible to people who can't view the images at all. So people stuck with an IE6 browser will still survive. You can write a FAQ answer explaining that if they upgraded to free software they'd see better support for the w3c standard image format.
According to title 17, an employer owns the copyright to "a work prepared by an employee within the scope of his or her employment." I don't know the case law myself, but I wouldn't expect this to be measured by whether you're using the company's computer, any more than I'd expect they would hold copyright to all phone conversations made on company phones.
Only if there are conspicuous terms on the outside the box, is there any case for the existence of a contract other than standard contract of sale. Even with conspicuous terms on the outside it's debatable.
In reality, Microsoft's CLR is only slightly better than the JVM at accommodating multiple languages. Better support is "planned for a future release", much like the 1993 promises of WinNT that came out in 2001. All the languages ported to the CLR had to be compromised somehow, same as those that compile to JVM bytecodes. I'm still hoping dotnet will push Sun to extend the JVM to be more acommodating of non-Java languages. For example, it would be fun to try full continuations in BRL pages.
As opposed to the Java world, where you have JSP, WebMacro, Velocity, Tea, etc. etc. in popular use, and a whole slew of other languages implemented on the JVM.
Couldn't the w3c recognize how much this would hurt them? I mean, look how irrelevant the Internet is now. If the IETF hadn't limited themselves to open standards like TCP/IP, etc., think how popular the Internet might be today! Everybody would be using it!
Since the original question related to handling 100+ concurrent requests, the service is likely an Internet-facing web site. In that arena, most companies do ditch Windows, even if they're using Exchange, etc. on their internal company servers. A "ditch Windows" answer is simply sharing the prevailing wisdom. If there's some reason why they can't ditch Windows in this situation, they should have said so in the question, since that's the obvious answer to expect.
You can use BRL that way. See the testsuite directory in the source distribution for how to process BRL files without any web framework. Additionally, there's a builtin function for LaTeX-escaping strings, in case you want really nicely formatted PDF reports, as I do. Additionally, when you embed code to generate an email within a file that generates a web page, the same nice template syntax is used as at the top level, unlike any similar technology that I'm aware of.
You can partially separate logic and presentation. How much separation is appropriate depends on the project...actually on individual instances within the project of logic/presentation relationships.
There are lots of people out there who do too little separation of presentation and logic. They'll end up with a better end result if they use Velocity, Freemarker or webmacro. There may also be people out there who produce overly bland user interfaces because they try too hard to separate presentation and logic. They would benefit from JSP, BRL, Tea, PHP, CF, or somesuch. Although with BRL it's easier to extricate the logic from the presentation if you start out with too little separation.
OK, enough ranting. It's just that this "100% separation" fiction is one of my pet peeves.
Except I don't do any consulting. I'm an employee.
Successful programming projects save companies lots of money. One successful project will only whet their appetite for more. I expect there will always be work for me, no matter how many overseas programmers compete.
Another post seems to indicate this was done via software to automatically detect defects. Many (most?) security defects cannot be detected automatically, as they involve using the software in an unintended way.
YANAL. IANAL. Yet we can still read the court decision to address some of our curiosity. You'll see that the EULA issue is, in fact, important.
Where patent enters into it is the possibility that the US Supreme Court declined to hear the case because it touches on software patents. The latest US Supreme Court case (Diamond v. Diehr, 1981), reaffirmed that software is not patentable. Lower court rulings have boldy contradicted this ruling, and the Supreme Court hasn't been willing to face up to the politically messy issue. Perhaps that's why they declined to hear this case, despite its sweeping implications. See Justice Dyk's dissent for a scary description of those implications.
See, here's another person who thinks stable and unstable are your only Debian choices. See also the earlier posts about stable servers vs less stable desktops. Nobody knows about the Debian testing distribution unless they hear about it from somebody else. Rather than write a long essay about how everybody needs to market Debian better, volunteer time to change Debian's web site to make the testing distribution more prominent. Then watch Debian's reputation change. The Debian testing distribution rocks.
Those new arrays are not necessary. They could have changed the language to include a simple declaration of what variables are inputs, like define-input in BRL. This eliminates all the security issues and is nearly as simple.
Um, how exactly did bar codes change Big Brother's powers dramatically? Only for bar codes was 1984 a significant year, not for RFIDs.
The latest word from the U.S. Supreme Court is that software patents are invalid (Diamond v. Diehr, 1981). Lower courts have contradicted this ruling since then, and the Supreme Court hasn't heard any relevant cases recently. Maybe if you could get your case up to the Supreme Court they would reinforce their 1981 ruling. Too bad lower courts have managed to make it "illegal" to "infringe" on patents that the country's highest court has ruled invalid.
I program professionally in Scheme, you insensitive clod!
(Seriously, I do.)
Ignore what the other poster said about converting dvi. Use pdflatex to go straight from latex source to pdf. The supertabular package matches so perfectly what you asked for in your first post, that I thought you might be trolling for a pdflatex answer.
I've used both MySQL and PostgreSQL. In my experience MySQL is not easier.
You should make sure your app is accessible to people who can't view the images at all. So people stuck with an IE6 browser will still survive. You can write a FAQ answer explaining that if they upgraded to free software they'd see better support for the w3c standard image format.
According to title 17, an employer owns the copyright to "a work prepared by an employee within the scope of his or her employment." I don't know the case law myself, but I wouldn't expect this to be measured by whether you're using the company's computer, any more than I'd expect they would hold copyright to all phone conversations made on company phones.
PostNuke security alert due to SQL Injection
Only if there are conspicuous terms on the outside the box, is there any case for the existence of a contract other than standard contract of sale. Even with conspicuous terms on the outside it's debatable.
In reality, Microsoft's CLR is only slightly better than the JVM at accommodating multiple languages. Better support is "planned for a future release", much like the 1993 promises of WinNT that came out in 2001. All the languages ported to the CLR had to be compromised somehow, same as those that compile to JVM bytecodes. I'm still hoping dotnet will push Sun to extend the JVM to be more acommodating of non-Java languages. For example, it would be fun to try full continuations in BRL pages.
As opposed to the Java world, where you have JSP, WebMacro, Velocity, Tea, etc. etc. in popular use, and a whole slew of other languages implemented on the JVM.
Couldn't the w3c recognize how much this would hurt them? I mean, look how irrelevant the Internet is now. If the IETF hadn't limited themselves to open standards like TCP/IP, etc., think how popular the Internet might be today! Everybody would be using it!