Archive for the ‘Java’ Category
It’s not just me because I found this post on MySQL forums -
In your release notes you mentioned that the binaries can be found here:
Unfortunately I am seeing an empty page there. Has this artifact ever
been uploaded somewhere?
MySQL MXJ Connector allows Java developers to easily and transparently embed MySQL database in a cross-platform manner in the installation package. Last release version 5.0.12 is available on maven mirror.
Has it just been discontinued permanently by Oracle? Although MySQL as an embedded database has limited functionality and SQLite is preferred, it makes sense to embed MySQL in some scenarios e.g. embedding database in a package which already targets MySQL.
Sun could’ve just downloaded MySQL from the site and run without paying .
Anyway, Sun buying MySQL is a big deal and a big surprise. Another slightly related acquisition news today is – Oracle buying BEA, the app server company. Incidentally, Oracle owns both InnoDB and BerkeleyDB – two of the better engine options of MySQL.
It’s a small not-very-useful exercise, but, as the result is unexpected for me – here it is.
I’ve created a web page where two images are served as static files, and two images are served by a Java Servlet. The images served as static files (top two images) are cached by the browser for future runs.
The results are as following:
The actual numbers are irrelevant, but the relative ratios consistently demonstrate that the web server “can” serve images much quicker (disregarding network latency) than the browser can retrieve them from cache. As expected, web servers serve static files quicker than they can serve Java Servlets.
Sidenote: damn, browser image resize is ugly.
I’ve downloaded Jetty Server Adapter for Eclipse recently. Jetty is supposedly very nimble Java-based HTTP Server and Servlet Container. I’m not sure if I’m doing it wrong, but I find code redeployment very slow and buggy when using Jetty on Eclipse. Even Jboss, another heavy duty application server, is bad on Eclipse with 15-25 second redeployment time.
So far I’ve found only Tomcat to be suitable for development with almost instant redeployment.
Another nuisance is that Jetty relies on the presence of PID file ( on my RHEL 4.2) to determine whether it’s running or not, which is, more often than not, inaccurate as I usually close Eclipse without shutting down Jetty server. Tomcat is much more stable in that sense. However, Jetty seems much more exciting to develop “for” (as opposed to “on”) as it has continuations, a very clever hack/feature.
I suppose that the preferred way to develop on Jetty is to use Maven, and Jetty Server Adapter will improve with future releases of WTP/Eclipse milestones.