added 2008 Fri May 16 16:55:30 by jaymeyer
Is your Java Application Server clustered? Why not? It should be, and your reasons for NOT clustering have vanished, so there’s no excuse. Cluster. Now.
Is your Java Application Server clustered? Why not? It should be, and your reasons for NOT clustering have vanished, so there’s no excuse. Cluster. Now.
added 2008 Thu May 15 20:50:32 by bloid
This time, we’ve asked our contributors the question: “In your experience with Comet development, what solution to a problem are you most proud of, and how did you accomplish it?”
This time, we’ve asked our contributors the question: “In your experience with Comet development, what solution to a problem are you most proud of, and how did you accomplish it?”
added 2008 Thu May 15 13:20:56 by mbreese
This post was on the front-page of dzone today: Bullet Proof Cookies. Did anyone actually read the article? This shows a horrible way to use cookies. Well, maybe not horrible, but at least it is certainly over-kill. Here are a couple of other techniques you can use to secure your cookies without the overhead of encrypting everything.
This post was on the front-page of dzone today: Bullet Proof Cookies. Did anyone actually read the article? This shows a horrible way to use cookies. Well, maybe not horrible, but at least it is certainly over-kill. Here are a couple of other techniques you can use to secure your cookies without the overhead of encrypting everything.
added 2008 Thu May 15 8:20:57 by scottbale
Detecting concurrency-related bugs and performance bottlenecks is hard, especially on clusters consisting of a large number of nodes. In an interview with Artima, Terracotta co-founder and CTO Ari Zilka explains the importance of visualization in cluster-based applications, and introduces Terracotta's open-source cluster visualizer tool.
Detecting concurrency-related bugs and performance bottlenecks is hard, especially on clusters consisting of a large number of nodes. In an interview with Artima, Terracotta co-founder and CTO Ari Zilka explains the importance of visualization in cluster-based applications, and introduces Terracotta's open-source cluster visualizer tool.
added 2008 Wed May 14 16:56:18 by madrense
How I dealt with the import of UTF-8 CSV files to the google appengine server.
How I dealt with the import of UTF-8 CSV files to the google appengine server.
added 2008 Wed May 14 11:04:30 by bloid
HTTP Channels is a transport protocol based on the existing messaging capabilities of HTTP and utilizes the concepts of REST for notification of resource changes. HTTP Channels is intended be a Comet solution for RESTful real time data synchronization architecture and can be used as a Bayeux transport, or it can be used stand-alone. HTTP Channels is designed to provide a mechanism for efficient and standards-based retrieval and monitoring of data and for receiving notification of changes to data with meaningful semantics.
HTTP Channels is a transport protocol based on the existing messaging capabilities of HTTP and utilizes the concepts of REST for notification of resource changes. HTTP Channels is intended be a Comet solution for RESTful real time data synchronization architecture and can be used as a Bayeux transport, or it can be used stand-alone. HTTP Channels is designed to provide a mechanism for efficient and standards-based retrieval and monitoring of data and for receiving notification of changes to data with meaningful semantics.
added 2008 Tue May 13 13:45:14 by mhenke
We are happy to announce that we have made our Open BlueDragon VMWare image available. The image contains: CentOS 5.1 (with all available upgrades as of 05/11/2008) Tomcat 5.5 MySQL 5.0.22 Apache 2.x and of course Open BlueDragon (build of 05/11/2008)
We are happy to announce that we have made our Open BlueDragon VMWare image available. The image contains: CentOS 5.1 (with all available upgrades as of 05/11/2008) Tomcat 5.5 MySQL 5.0.22 Apache 2.x and of course Open BlueDragon (build of 05/11/2008)
added 2008 Tue May 13 6:48:47 by bloid
In a number of projects, we have to use @Remote EJB's. There are pros and cons for using @Remote EJB's, but in some cases the pros outweigh the cons. At least in GlassFish, you can boost the performance of remote EJB's relatively easily.
In a number of projects, we have to use @Remote EJB's. There are pros and cons for using @Remote EJB's, but in some cases the pros outweigh the cons. At least in GlassFish, you can boost the performance of remote EJB's relatively easily.
added 2008 Mon May 12 16:53:34 by lijinjoseji
A small comparision between TWO famous continous integration tools.
A small comparision between TWO famous continous integration tools.
Sponsors
More tags
Technology Apple Hardware Linux Programming Security Software unix-linux ajax how-to javascript php java tools .net trends frameworks research gui web design ruby open source reviews web 2.0 eclipse other languages perl python humor announcement News Microsoft Windows usability database standards Video Internet free web services web rails mysql mail Network personality blog storage flash hosting tips freeware website file tool ubuntu howto dallas suse novell Streaming tutorial performance opensource service webdev Bloggers sysadmin application blogger opinion virtualization DNS bittorrent hatena postfix install domain widgets networking thinclient lamp nas methodology tecnologia cluster apache servers http webserver akismet comet sidebar datacenter sakura conversations mail server socket c10k spam protection
added 2008 Mon May 12 6:49:13 by springfan
What is SpringSource thinking? Why are they betting everything on OSGi? What's so special about the Spring 2 Application Platform? Read this article to get your bearings.
What is SpringSource thinking? Why are they betting everything on OSGi? What's so special about the Spring 2 Application Platform? Read this article to get your bearings.
added 2008 Fri May 9 21:14:47 by jeyrb
Viewpoint on Spring S2AP and OBR announcements from OSGi Alliance's senior architect
Viewpoint on Spring S2AP and OBR announcements from OSGi Alliance's senior architect
added 2008 Fri May 9 14:17:50 by bloid
In this blog, I will describe some of the EJB 3.1 features that are available in GlassFish V3. For a full list of what is planned in EJB3.1 please refer to Ken's blog Note: Before, you run any of the EJB 3.1 applications ensure that you follow the steps outlined in Installing EJB container in GlassFish V3
In this blog, I will describe some of the EJB 3.1 features that are available in GlassFish V3. For a full list of what is planned in EJB3.1 please refer to Ken's blog Note: Before, you run any of the EJB 3.1 applications ensure that you follow the steps outlined in Installing EJB container in GlassFish V3
added 2008 Fri May 9 12:52:05 by dan
There have been several blog posts recently about class-loading issues apparently linked the use of the Sun-Java 1.6 (6.0) JVM. Mark Mandel has a detailed article on this here. Before seeing this article we had been working on optimizing a ColdSpring-ModelGlue-Reactor application. We blogged our progress in this article. We thought a reality check was a good idea and ran some load tests comparing this same application performance in Java 1.5 and 1.6. Once again we observed better performance in 1.6; here are the results. These results are for a 50 Virtual User (vUser) Test for 1 hour with 8 second think time (delay between clicks) comparing Java 1 5 to 1.6. Firstly Java 1.5 Total Number of Clicks: 13,345 (0 Errors) Average Click Time of all URLs: 5,298 ms
There have been several blog posts recently about class-loading issues apparently linked the use of the Sun-Java 1.6 (6.0) JVM. Mark Mandel has a detailed article on this here. Before seeing this article we had been working on optimizing a ColdSpring-ModelGlue-Reactor application. We blogged our progress in this article. We thought a reality check was a good idea and ran some load tests comparing this same application performance in Java 1.5 and 1.6. Once again we observed better performance in 1.6; here are the results. These results are for a 50 Virtual User (vUser) Test for 1 hour with 8 second think time (delay between clicks) comparing Java 1 5 to 1.6. Firstly Java 1.5 Total Number of Clicks: 13,345 (0 Errors) Average Click Time of all URLs: 5,298 ms
added 2008 Fri May 9 12:39:40 by dan
Clustering in particular with ColdFusion and JRun can get fairly complicated pretty fast and I urge all who are going to embark on clustering to plan out how you want to cluster and why. Another key issue is to make sure when we are creating a web application that it designed and engineered from day one with clustering in mind. I have helped so many clients who hit major problems when they start building clusters, largely because the application was too tightly coupled to the environment it is running in. Hard-coded directory paths would be a classic example. In this blog posting I wanted to illustrate an interesting concept, well two in reality, Horizontal Clustering and Vertical Clustering. Let's look at a diagram....
Clustering in particular with ColdFusion and JRun can get fairly complicated pretty fast and I urge all who are going to embark on clustering to plan out how you want to cluster and why. Another key issue is to make sure when we are creating a web application that it designed and engineered from day one with clustering in mind. I have helped so many clients who hit major problems when they start building clusters, largely because the application was too tightly coupled to the environment it is running in. Hard-coded directory paths would be a classic example. In this blog posting I wanted to illustrate an interesting concept, well two in reality, Horizontal Clustering and Vertical Clustering. Let's look at a diagram....
added 2008 Fri May 9 9:38:05 by dan
I have added several blog postings here before on the theories of High-Availability (HA) and Clustering. In this series of blog postings I will be attempting to create dedicated postings for the following scenarios. Please keep in mind that there will be alternative ways to do these things and what I am showing here is drawn from my experiences from either creating clusters for clients or working on existing clusters Here are the scenarios I will be posting on... Setting up a two instance cluster from a fresh install of ColdFusion Load testing a two instance cluster on Java 1.6 (6.0) using the Round Robin algorithm Load testing a two instance cluster on Java 1.5 (6.0) using the Round Robin algorithm
I have added several blog postings here before on the theories of High-Availability (HA) and Clustering. In this series of blog postings I will be attempting to create dedicated postings for the following scenarios. Please keep in mind that there will be alternative ways to do these things and what I am showing here is drawn from my experiences from either creating clusters for clients or working on existing clusters Here are the scenarios I will be posting on... Setting up a two instance cluster from a fresh install of ColdFusion Load testing a two instance cluster on Java 1.6 (6.0) using the Round Robin algorithm Load testing a two instance cluster on Java 1.5 (6.0) using the Round Robin algorithm
added 2008 Thu May 8 1:53:32 by bloid
First, hats off to Rod, Adrian and the others. It's very nice and very much in line with where most people see this all going in the next few years.
First, hats off to Rod, Adrian and the others. It's very nice and very much in line with where most people see this all going in the next few years.
added 2008 Wed May 7 16:01:27 by alevaux
Tomcat is probably one of the more widely used pieces of open source infrastructure and it's a great boon to our productivity. Sometimes, though, a deep-rooted problem can sneak up on you and drag you into a sleep-deprived night of frantic web searching.
Tomcat is probably one of the more widely used pieces of open source infrastructure and it's a great boon to our productivity. Sometimes, though, a deep-rooted problem can sneak up on you and drag you into a sleep-deprived night of frantic web searching.
added 2008 Wed May 7 9:26:45 by shabda
Let’s see what a Killer app gives you. 1. It fills a big niche, so people are forced to learn your language/framework. 2. It forces the Hosting company to support your language/framework. ............
Let’s see what a Killer app gives you. 1. It fills a big niche, so people are forced to learn your language/framework. 2. It forces the Hosting company to support your language/framework. ............
added 2008 Wed May 7 4:25:29 by boblozano
Lots of conversation about the Spring Application Platform ... some reasonable, some crazy, some personal, some all of the above. This post summarizes some of the points of view and raises a couple of questions.
Lots of conversation about the Spring Application Platform ... some reasonable, some crazy, some personal, some all of the above. This post summarizes some of the points of view and raises a couple of questions.
added 2008 Tue May 6 12:22:54 by bloid
So, Spring Source has been able to keep a secret from us :-) Secretly, they have been developing what looks a lot like a new application server, not like the JEE market, but with the springframework at its core. A well kept secret, which I did not see coming, even though we might have been able to, given the portfolio of products and people now employed at Spring Source.
So, Spring Source has been able to keep a secret from us :-) Secretly, they have been developing what looks a lot like a new application server, not like the JEE market, but with the springframework at its core. A well kept secret, which I did not see coming, even though we might have been able to, given the portfolio of products and people now employed at Spring Source.
added 2008 Tue May 6 11:27:59 by jeyrb
Another take on SpringSource's recent announcement of s2ap
Another take on SpringSource's recent announcement of s2ap
added 2008 Tue May 6 2:16:49 by bloid
I like to do things the right and clean way. And shutting down a service under Linux is done by calling the start-/stop-script under /etc/init.d with the parameter stop. Even graphical front-ends, may they be YAST or webmin or whatever stick to this rule. The advantage is, the whole know-how of how to shutdown one specific service is hidden in the start-/stop-script. Killing a process directly is real evil, because the process (and dependend processes) don't get the chance to do whatever they have to before shutting down. Otherwise databases get corrupted, stale files claim disk space, memory is hogged by zombie processes and the like.
I like to do things the right and clean way. And shutting down a service under Linux is done by calling the start-/stop-script under /etc/init.d with the parameter stop. Even graphical front-ends, may they be YAST or webmin or whatever stick to this rule. The advantage is, the whole know-how of how to shutdown one specific service is hidden in the start-/stop-script. Killing a process directly is real evil, because the process (and dependend processes) don't get the chance to do whatever they have to before shutting down. Otherwise databases get corrupted, stale files claim disk space, memory is hogged by zombie processes and the like.
VirtualBox
ma.gnolia tags : tools 08102006 widgets api service list Software portable application @new creativity pixar animation innovation css rss OSX photography pictures guide advice *features web webdesign css design inspiration search addictomatic twitter friends visualization tool Linux opensource server
added 2008 Mon May 5 7:00:00 by unknown user
Saved By: Markus Heurung | View Details | Give Thanks
Saved By: Markus Heurung | View Details | Give Thanks
added 2008 Sat May 3 11:29:55 by bloid
There were lots of great comments on the CSS Caching article. I learned a lot from those comments, so I wanted to clear up some of the misunderstanding and highlight some of the great tricks other folks shared.
There were lots of great comments on the CSS Caching article. I learned a lot from those comments, so I wanted to clear up some of the misunderstanding and highlight some of the great tricks other folks shared.
added 2008 Sat May 3 1:53:55 by fdiotalevi
If you're looking for a fast and easy way to run your webapp, without needing to install and administer a Jetty distro, then look no further, the Jetty Runner is here! The idea of the Jetty Runner is extremely simple - run a webapp from the command line using a single jar and as much default configuration as possible:
If you're looking for a fast and easy way to run your webapp, without needing to install and administer a Jetty distro, then look no further, the Jetty Runner is here! The idea of the Jetty Runner is extremely simple - run a webapp from the command line using a single jar and as much default configuration as possible:
added 2008 Fri May 2 19:08:15 by sbc
In the past week+ the whole business about Twitter scalability & reliability came to a head. Bob Lozano provides an interesting persepctive on what's required to build a scalable micro-blogging service. He proposes five key ideas for building the next Twitter++...
In the past week+ the whole business about Twitter scalability & reliability came to a head. Bob Lozano provides an interesting persepctive on what's required to build a scalable micro-blogging service. He proposes five key ideas for building the next Twitter++...
added 2008 Fri May 2 15:40:37 by puredanger
Our message bus project was more than just replacing JMS with a POJO messaging system. It’s a whole piece of infrastructure designed to make it easy for different folks to do their jobs. How did we do this and why do the next couple of paragraphs sound like I’m bragging? Because many of the features we implemented were recently announced in a new open source project (more on that later).
Our message bus project was more than just replacing JMS with a POJO messaging system. It’s a whole piece of infrastructure designed to make it easy for different folks to do their jobs. How did we do this and why do the next couple of paragraphs sound like I’m bragging? Because many of the features we implemented were recently announced in a new open source project (more on that later).
added 2008 Thu May 1 23:14:50 by geertjan
Let's dip our toes into the SpringSource Application Platform's Beta program. "Legacy" archives, i.e., WARs and EARs, are advertized as being supported, so theoretically one should be able to deploy apps even though they're not OSGi bundles. The Beta program, live since yesterday, seems a good place to start.
Let's dip our toes into the SpringSource Application Platform's Beta program. "Legacy" archives, i.e., WARs and EARs, are advertized as being supported, so theoretically one should be able to deploy apps even though they're not OSGi bundles. The Beta program, live since yesterday, seems a good place to start.
added 2008 Thu May 1 10:21:23 by bloid
At the beginning of 2007 we began discussing possible alternatives to the monolithic and heavyweight application servers with which Enterprise Java has become synonymous. Customers were looking for a platform that was lightweight, modular and flexible enough to meet their development and deployment needs.
At the beginning of 2007 we began discussing possible alternatives to the monolithic and heavyweight application servers with which Enterprise Java has become synonymous. Customers were looking for a platform that was lightweight, modular and flexible enough to meet their development and deployment needs.
12345678910111213 ... 27 »
