Managing multiple internal projects using Maven (Switching from ant/ivy) Local Storage. You are here: Home Dive Into HTML5 Diving In Persistent local storage is one of the areas where native client applications have held an advantage over web applications.
For native applications, the operating system typically provides an abstraction layer for storing and retrieving application-specific data like preferences or runtime state. These values may be stored in the registry, INI files, XML files, or some other place according to platform convention. If your native client application needs local storage beyond key/value pairs, you can embed your own database, invent your own file format, or any number of other solutions. Practical Introduction into Code Injection with AspectJ, Javassist, and Java Proxy. The ability to inject pieces of code into compiled classes and methods, either statically or at runtime, may be of immense help.
This applies especially to troubleshooting problems in third-party libraries without source codes or in an environment where it isn’t possible to use a debugger or a profiler. Code injection is also useful for dealing with concerns that cut across the whole application, such as performance monitoring. Memory leaks are easy to find. Building Filesystems the Way You Build Web Apps (Ksplice Blog) FUSE is awesome.
While most major Linux filesystems (ext3, XFS, ReiserFS, btrfs) are built-in to the Linux kernel, FUSE is a library that lets you instead write filesystems as userspace applications. When something attempts to access the filesystem, those accesses get passed on to the FUSE application, which can then return the filesystem data. It lets you quickly prototype and test filesystems that can run on multiple platforms without writing kernel code. You can easily experiment with strange and unusual interactions between the filesystem and your applications.
Screenshots. Squares Aren’t Rectangles? A Common Misunderstanding of Object Oriented Design From MSDN Magazine. While reading the recent Dec 2010 issue of MSDN magazine, I found an article (Multiparadigmatic .Net, Part 4: Object Orientation) with misunderstandings on object oriented design.
Using XML and Jar Utility API to Build a Rule-Based Java EE Auto-Deployer. By Colin (Chun) Lu 11/16/2007 Introduction Today's Java EE application deployment is a common task, but not an easy job.
If you have ever been involved in deploying a Java EE application to a large enterprise environment, no doubt you have faced a number of challenges before you click the deploy button. Home - Janino.
Java device driver. Image procesing. JUV NativeAccess SDK demo (webcam capture) V1Benchmarks - kryo - Benchmarks for version 1.x - Fast, efficient Java serialization and cloning. The results below were obtained using the thrift-protobuf-compare project.
There you will find the source for the benchmarks used to generate the charts displayed here. Architecture. Security. Live-android - A LiveCD for Android. Improving J2EE Application Performance. Introduction You delivered the application to the users and they are now using it every day.
Early feedback has indicated that the performance of the application does not meet the requirements. The service level agreement called for a maximum response time of five seconds per request. "Inconceivable! " After all you tried the application yourself and found the response time to always meet this metric. This article describes how to achieve a high level of performance in a J2EE application, independent of which Application Server you use. Choose your performance goals It is always best to choose the project goals before development starts. If you are building an n-tier application that has the goal of supporting clients over slow connections (dial-up modems), then you may employ techniques such as compressing as much information into individual TCP/IP packets as possible.
In most applications, performance is dependent on several factors. Follow a structured approach to improving performance. Introduction to Java Module System in Java 7.0. GuavaExplained - guava-libraries - Landing page for Guava explanations. - Guava: Google Core Libraries for Java 1.6+ The Guava project contains several of Google's core libraries that we rely on in our Java-based projects: collections, caching, primitives support, concurrency libraries, common annotations, string processing, I/O, and so forth.
Each of these tools really do get used every day by Googlers, in production services. But trawling through Javadoc isn't always the most effective way to learn how to make best use of a library. Here, we try to provide readable and pleasant explanations of some of the most popular and most powerful features of Guava. ProxyFactory (Javassist API)
Factory of dynamic proxy classes.
This factory generates a class that extends the given super class and implements the given interfaces. The calls of the methods inherited from the super class are forwarded and then invoke() is called on the method handler associated with instances of the generated class. The calls of the methods from the interfaces are also forwarded to the method handler. Think again before adopting the commons-logging API. By Ceki Gülcü, November 14th, 2002, last updated October 29th, 2009, © All rights reserved Introduction Given that log4j is such a low-level library, most organizations are hesitant to tie their code to log4j, especially considering the new logging API included in JDK 1.4.
Project Lombok. State of the Collections. April 2012 This is an informal overview of the major proposed library enhancements to take advantage of new language features, primarily lambda expressions and extension methods, specified by JSR 335 and implemented in the OpenJDK Lambda Project. Modularization in java 8. To Java SE 8, and Beyond!
The Java Specialists' Newsletters.