Slashdot Mirror

← Back to Domains

Domain: advisor.com

Stories and comments across the archive that link to advisor.com.

Comments · 6

  1. Re:Microsoft is now irrelevent by metamatic · · Score: 1 · on Ballmer: 'We'll catch Google'
    ...and that SQL Server development has ground to a halt (ceding victory to Oracle)

    You mis-spelled IBM :-)

  2. Anyone considering JSP should probably read... by release7 · · Score: 1 · on JSP and Tag Libraries for Web Development

    JSP is probably not the way to go in the first place. This informative article, JSP: A Total Waste of Time? sums up some of the core problems pretty nicely.

  3. Re:Of course! by NineNine · · Score: 2 · on Will Open Source Ever Become Mainstream?

    People hate Microsoft

    Wrong. Wrong. Wrong Wrong. Wrong. Wrong. etc., etc. You're wrong.

    Red Hat is one of the fastest growing companies in America

    Wrong. Wrong. Wrong.

    Sorry to make you look so incredibly wrong, but you posted first. I just couldn't let that fly. By the way, what planet do you live on, exactly?

  4. Re:Ridiculous! by SEWilco · · Score: 1 · on Reuters Accused Of Hacking For Typing In URL
    Besides, isn't 'regulating access to private information on a public website' what htaccess was for?

    The .htaccess controls file access under Apache. Others report that this company is using Lotus Domino, which does have a different way to restrict file access.

    But is it hacking to try "Q3" instead of "Q2" in http://www.intentia.com/w2000.nsf/(files)/Intentia _02_Q3_us.pdf/$FILE/Intentia_02_Q3_us.pdf? An automated script might be monitoring release of the next file -- it certainly would not be hard to predict the file name and create the script.

  5. Re:Simple Explanation by Misha · · Score: 2 · on Lineo near Death

    There are likely to be many others like it.

    what? you didn't get the memo? I'd say these guys are like many before them.

  6. Making the same mistakes all over again by Carnage4Life · · Score: 3, Insightful · on Interoperable P2P: Jxta
    The problem I have with distributed computing technologies from Sun and the other Unix companies is that they are typically never fully standardized by vendors. CORBA suffered from the fact that the spec was too generic and yet to complex and thus didn't enforce that ORBs should provide enough default services which lead to all sorts of interesting vendor lock in as its almost impossible to find two ORBs that implement the same exact set of services.

    Although J2EE decided to go a different route by specifying a comprehensive list of minimum requirements it is sizable enough that no two vendors currently completely implement all of the same functionality (or at least not the last time I checked).

    Jxta seems to be taking the generic-ness route which from experience leads to incompatible implementations and vendor lock-in. Particularly telling where the following excerpts from the article
    In other words, a Jxta application that meets the minimum specified interoperable requirements superficially and does not interoperate in any meaningful way with others can still be in accord with the Jxta specification. However, it is anticipated that the viral growth of P2P applications and services will force vendors to embrace interoperability as a key product feature. The consequences of this design decision are left to be tested by the trials and tribulations of open market forces.
    Sounds like a journey that is starting with the wrong step to me.