Most antispam software seems to be fairly reactionary - wither it is based on keyword patters, urls, sender, ip, or the checksum of the message a certain amount of spam has to first be sent and identified before additional messages will be tagged and blocked. Spf, domainkeys, etc... requires a certain percentage of the Internet to adopt before they will be truely effective.
What do you see on the horizon as the next big technique to battle spam? How will this affect legitimate users on the Internet?
I've seen this exact thing in the wild already. One of my customer is storing large amounts of mpeg movies. They were using md5sum to verify file contents for network transfers. This worked great until there was a power failure on of the remote systems. Everything passwd the md5sum perfect, except halfway through the clip you would lose video. I haven't relied on md5sum for over a year now as a result.
BEA lists the IBM JDK as their platform requirements for the Linux platform. We found that Tomcat 3.3.1 / IBM 1.3.1 would serve around 1.2 million page views a day on a dual proc Linux machine.
I don't care what anyone says, this is definately ready for prime time, and in fact was faster than BEA WLS5.1 running on E420Rs.
Porting to BEA?!?! How funny... my company is currently porting from BEA to Tomcat/JBoss. We are running everything from WLS5.1-WLS7, Commerce server and WLI.
BEA is so kind as to put there own interpertation of standards (M$ anyone?) inside of their app servers. The custering configuration is awkward and limiting (try restarting a VM if you are serving real traffic. The listener starts before the VM is ready oops.) They don't allow a component architecture, the JMS implementation is dog slow (not to mention that it will only run on one VM).
I think it's a great product for $10K a CPU. But then again we're serving 2 million transactions a day on a pair of Tomcat servers.
Slashdot Mirror
Most antispam software seems to be fairly reactionary - wither it is based on keyword patters, urls, sender, ip, or the checksum of the message a certain amount of spam has to first be sent and identified before additional messages will be tagged and blocked. Spf, domainkeys, etc... requires a certain percentage of the Internet to adopt before they will be truely effective.
What do you see on the horizon as the next big technique to battle spam? How will this affect legitimate users on the Internet?
I've seen this exact thing in the wild already. One of my customer is storing large amounts of mpeg movies. They were using md5sum to verify file contents for network transfers. This worked great until there was a power failure on of the remote systems. Everything passwd the md5sum perfect, except halfway through the clip you would lose video. I haven't relied on md5sum for over a year now as a result.
See this is all part of the strategy... sue IBM for infringing on your IP, so everyone will buy your product so that they won't be liable.
But wait, release a GPL product with your IP embedded in it... doesn't that mean that your IP is now GPL?
Boy am I confused, so SCO is suing IBM for writing software that they are now selling for themselves and benifiting from.
Where can I buy tickets to the court case? I can't wait for this!
BEA lists the IBM JDK as their platform requirements for the Linux platform. We found that Tomcat 3.3.1 / IBM 1.3.1 would serve around 1.2 million page views a day on a dual proc Linux machine.
I don't care what anyone says, this is definately ready for prime time, and in fact was faster than BEA WLS5.1 running on E420Rs.
Porting to BEA?!?! How funny... my company is currently porting from BEA to Tomcat/JBoss. We are running everything from WLS5.1-WLS7, Commerce server and WLI.
BEA is so kind as to put there own interpertation of standards (M$ anyone?) inside of their app servers. The custering configuration is awkward and limiting (try restarting a VM if you are serving real traffic. The listener starts before the VM is ready oops.) They don't allow a component architecture, the JMS implementation is dog slow (not to mention that it will only run on one VM).
I think it's a great product for $10K a CPU. But then again we're serving 2 million transactions a day on a pair of Tomcat servers.
Why not do a real port and go to c#?
Beware....
Congrats!!
Is this the birth of a new section where users can propose to their others online? I see a huge willyoumarryme.com IPO in the future.
Of course you should try it, you just might like it.
l e/images1219 i386
images01-la1# uname -a
FreeBSD images01-la1 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Tue Dec 19 11:36:03 PST 2000 root@images01-la1.ussearch.com:/usr/src/sys/compi
images01-la1# uptime
11:26AM up 407 days, 51 mins, 1 user, load averages: 0.01, 0.21, 0.27