|Would You Ever Use A Java Applet Cart?|
Try to gather some info on whether or not these are widely used. I've seen CGI, PHP, and ASP carts - but rarely see Java carts.
Am I just not looking hard enough?
Thanks in advance.
Speaking only anecdotally and from personal experience, some people disable Java due to security concerns. I personally hate Java myself. Some more technical folks here might be able to expound on that.
It was easy to install though - I even did it myself (which is saying something!)
I was referring to Java.
Java applets and JS are completely separate animals - but the cart I am reviewing, I assume, is an applet that uses some sort of JS for validation?
It completely oddball, that's why I started this thread.
Java is a horrible choice for a general purpose shopping cart/online store. There are virtually no advantages and too many disadvantages to list (complex, slow, inaccessible, inflexible, etc.).
"Java is a horrible choice for a general purpose shopping cart/online store. There are virtually no advantages and too many disadvantages to list (complex, slow, inaccessible, inflexible, etc.)."
not sure why pbreit feels this way. java and the MVC model allows for one to code an excellent and quite flexible shopping cart. not to mention the built in jvm secure functions are another advantage.
inaccessible? not sure what is meant by this.
granted java is not as easy to manipulate for non-java programmers, but that should be part of the decision making process.
There's nothing wrong with Java, for shopping carts or any other application, but using a Java applet when you don't need to is about as wise as using an ActiveX object, i.e., not very.
If you're putting up a website, you're going to be best served using technologies that stay on your server, under your control. A Java applet or ActiveX object is running on the client's machine, is slower than dynamic HTML, and can generally be duplicated on the server side with minimal effort. The only advantage I can see to using applets/ActiveX is that they can be integrated into your site with fewer steps. To my mind, that's not enough of a bonus to justify this method.
As far as JSP/Servlet carts, I think you're not looking hard enough.
I must defend the use of "Java" for shopping cart technology.
For instance, our company (why we can't name our products if they are relevant to the thread baffles me), has developed the leading mid-market ecommerce solution for the J2EE platform. It is written with Java using servlets and JSP. The benefits of which are open standards (no hardware restrictions as it will run on anything: Windows, Linux, Unix, Mac etc. and no Database restrictions as it will use Oracle, MS SQL, mySQL, DB2 etc.)
As for Java being slow, yes it has that notariety within client side applications, but when using web technologies such as JSP to deliver the data, there is no performance hindrance.
Java should be seriously considered as a ecommerce technology as it scales much better than proprietary languages.
|Would You Ever Use A Java Applet Cart? |
No way. even online banks that where about the only people are getting rid of this.
Basically you have to download the whole application from the server to the workstation and then run the software on your workstation. It might work, (Java: write once, debug everywhere) but why take the chances?
Sun itself very soon realized that for the broad market java appleets where a non-starter, so they introduced servlets and JSP to handle the work on the server.
Never. (note that you can have a Java cart without it being an applet, it can be servlets, and that's fine but usually expensive).
The problem in a nutshell is the impact of functionality on applet size. The more functionality, the bigger the applet and the longer it takes to download. A half decent cart would be abandoned by most shoppers before it has even finished downloading. One that is simple enough to download quickly will be abandoned as soon as they see how primitive it is.