|the big problem is still
|there: it'll run piss-poor with Tomcat. It doesn't really matter what fancy
|stuff you can think up with that crap hanging around.
yes and no.
no, the base for webservices is the future of JBoss, ejb is but a
personality ( a service) and servlet is another one. it is just a bad
container, we can get others... but read below.
You are right that today the quality of the http stack is a problem, we get
bloated code coming out of apache, even the guys at sun say that apache is
not a success since they pay all the developers and we need something
meaner and leaner.
It is a shame because I think they are really doing quality work with all
the XML thingies... what they miss is a rickard qbert jumping up and down
and a marc furry setting it all ablaze :)
more than slow it has become boring, open source as yet another stupid job?
lol...
|There, I said it, it pisses me off. The J2EE stack is a dream but nothing
|more unless Tomcat is fixed.
hey that is a real project "rickard-size"... why don't you take 2 weeks off
and rewrite a servlet container (ok maybe 3 weeks ;-). I truly believe we
can make something kick ass in JBoss kiddo.
I would write the http layer as an MBean that puts out requests on the JMX
bus (btw we use it as a bus) and servlet would be a container on that bus
and the stack of interceptors is there, similar to what you did in JBoss
2.0. A jdk1.4 nbio http stack, can you feel it?
I really think it would take you 3 weeks (ok maybe 4 weeks)...
|>there I said it, it pisses me off, get off your butt and produce something
|>real ;-)
|
|
|I am, just not right here. Get some perspective dude.
yeah right ...
pffffff@#$@ af#$$$da dsfa$#@&&)afd pffffffff!
starting a JBoss servlet container with jdk1.4 nbio would really be
something big enough for ya!
you are wasting your (valuable) time and talent
PLgHttpCode
marcf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
