Then again, from a purely business/economical perspective that
approach makes a lot of sense. And up until recently, Moore's law
would provide scalability as a function of time; cheaper, more
predictable and less risky than tinkering with the deployed software.
Also worth noting, although Sun wou
And the general attitude of some ops people (and managers, and who
ever else has influence) is, "if it ain't broke, don't fix it".
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to t
I'd say a more likely reason a lot of companies have not shifted to
haven't shifted to Java 6 on the server is that ~35% of the app server
market belongs to IBM Websphere, the latest version of which only
supports Java 1.5. Most large Enterprises just can't go to 6.
On May 10, 8:54 pm, Mark Derr
Outside of Grizzly, which is based on NIO, of course, I think many folk
have avoided NIO entirely due to various items like this.
--
Jess Holle
John Wright wrote:
> We've been using it in a production environment for 2 years with no
> issues.
>
> Its much faster and very stable. We've used it on
We've been using it in a production environment for 2 years with no
issues.
Its much faster and very stable. We've used it on Windows and Linux.
We don't use NIO though.
On May 11, 7:07 am, Eric Angel wrote:
> A company I worked for a few years made the switch to java 6 and haven't had
> any i
A company I worked for a few years made the switch to java 6 and haven't had
any issues. Granted, it's a web app that isn't disk IO heavy. We made the
switch because the performance improvements offered by java 6.
On Sun, May 10, 2009 at 12:54 PM, Mark Derricutt wrote:
> Hey all,
>
> A number
