Actually, I have looked at NetMeter, I used to work at the AG Group and was there when it was originally developed. It has a plugin architecture that allows you to not only make plugins for sounds, but also for graphs and yes, one of the first plugins was a sound plugin, the graphs actually came later.
Anyway, the point of my original posting was to say that the idea isn't new and that Peep is just copying an idea that has been around for a long time. Yes, NetMeter it is more than 4 years old (more like 6)...
WildPackets (previously known as the AG Group) NetMeter product has been able to do this (and much much more) for years now. It is nice to see someone taking someone else's idea and getting credit for it. Not.
We don't need EJB Server representation. There are already 2+ OSS EJB projects out there (I know, I host the CVS and mailing lists for one of them on my machines...JBoss). Not having it directly under the ASF, isn't doing us any harm at all because you can simply download the EJB servers from other locations. Big deal. Also, in my personal opinion only, EJB is a nasty buzz word that IS managers like to throw around. Only about 1% of the entire web application arena really needs it, the rest of the people who are developing on it are kidding themselves and wasting time/resources. It is entirely possible to have 100% stable servlet web applications without the need for the bulk that EJB adds. I wish that more people would wake up and more correctly evaluate the technologies they are using for the applications they are building instead of simply going along with Sun's marketing engine blindfolded. Yes, Sun does make good technologies, but not everyone has to use them for all cases. -jon
Hello all. I just want to make sure that it is clear that this is excellent news. Having the members of the ASF involved with Sun's decision making process at a high level is much better than not having any OSS representation at all at any level.:-) The future of Java on the server side is very bright. Those of you who are complaining about Java being slow have probably never used it on the server side (ie: servlets) which is the part that we are focusing on. It is quite fast and extremely stable and scalable. java.apache.org, jakarta.apache.org and xml.apache.org are the three main Apache projects that are clearly focused on Java technologies. java.apache.org and jakarta.apache.org will eventually be merged together and the entire Apache Project will be a very powerful OSS voice in the Java world. The Jakarta project (which was originally based on software contributed by Sun) has already proven to be extremely successful with >50k downloads of the Tomcat servlet engine per month and a lot of development/user support from the OSS community. Keep an eye on us. We are doing cool things for the OSS world. -jon (a proud member of the ASF)
Anyway, the point of my original posting was to say that the idea isn't new and that Peep is just copying an idea that has been around for a long time. Yes, NetMeter it is more than 4 years old (more like 6)...
WildPackets (previously known as the AG Group) NetMeter product has been able to do this (and much much more) for years now. It is nice to see someone taking someone else's idea and getting credit for it. Not.
http://www.wildpackets.com/products/netmeter
We don't need EJB Server representation. There are already 2+ OSS EJB projects out there (I know, I host the CVS and mailing lists for one of them on my machines...JBoss). Not having it directly under the ASF, isn't doing us any harm at all because you can simply download the EJB servers from other locations. Big deal. Also, in my personal opinion only, EJB is a nasty buzz word that IS managers like to throw around. Only about 1% of the entire web application arena really needs it, the rest of the people who are developing on it are kidding themselves and wasting time/resources. It is entirely possible to have 100% stable servlet web applications without the need for the bulk that EJB adds. I wish that more people would wake up and more correctly evaluate the technologies they are using for the applications they are building instead of simply going along with Sun's marketing engine blindfolded. Yes, Sun does make good technologies, but not everyone has to use them for all cases. -jon
Hello all. I just want to make sure that it is clear that this is excellent news. Having the members of the ASF involved with Sun's decision making process at a high level is much better than not having any OSS representation at all at any level. :-) The future of Java on the server side is very bright. Those of you who are complaining about Java being slow have probably never used it on the server side (ie: servlets) which is the part that we are focusing on. It is quite fast and extremely stable and scalable. java.apache.org, jakarta.apache.org and xml.apache.org are the three main Apache projects that are clearly focused on Java technologies. java.apache.org and jakarta.apache.org will eventually be merged together and the entire Apache Project will be a very powerful OSS voice in the Java world. The Jakarta project (which was originally based on software contributed by Sun) has already proven to be extremely successful with >50k downloads of the Tomcat servlet engine per month and a lot of development/user support from the OSS community. Keep an eye on us. We are doing cool things for the OSS world. -jon (a proud member of the ASF)