on 2/1/00 10:50 AM, Stephen Adkins <[EMAIL PROTECTED]> wrote:
> QUESTIONS
>
> * How does JServ+Turbine compare to commercial web application
> server packages?
It really doesn't attempt to. As you know, we have already ported two of
Weblogic's API's (dbKona -> Village/Town) and (htmlKona ->ECS).
You can run Turbine on top of Weblogic without problems. Turbine isn't an
app server, it is a MFC style framework and collection of code.
> * How does it compare to BEA WebLogic in particular?
Again, this is preference. I used to use Weblogic's server for doing servlet
development. It is quite good and very stable. I did find/report about 5-6
bugs that they fixed and also didn't give me credit for finding. I also
spent quite a lot of time figuring out why the bugs existed which I wouldn't
have done if I had source code. ;-)
> * Under what technical or project conditions would you recommend
> one or the other?
If you need commercial level support, then go with BEA. Otherwise, go with
OS solutions.
> * Would it ever make sense to use both? (or do they overlap too much)
Yes. They do overlap, but that isn't a bad thing. Imagine being able to make
choices and just use the parts of each that you like the best.
> * What are the features/capabilities which are lacking in
> JServ+Turbine that are available BEA WebLogic? vice-versa?
We don't pretend to go the EJB server route. Weblogic implements newer
versions of the Servlet API than JServ does (I have yet to find this as a
negative thing though). They have some other API's that are more complete
than what we have, such as GlobalCache and Cron / Scheduler functionality.
Weblogic doesn't have the same level of load balancing and distributed
n-tier that JServ has though. They do it in a different way that I
personally don't like because it is very specific to them.
Oh yea, one MAJOR problem with Weblogic for me is that if you decide to go
that route, you are locked into their products with no way out. If you go
the Turbine route, you have the source code. So, while you might be locked
into the Turbine model, you still can take your code and use it on other
projects without worry. For example, say you have a site that you develop in
house and one day you decide to open source it. If you used Weblogic
specific parts, then you are screwed.
> If JServ+Turbine is sufficiently functional/scalable, I would prefer
> to go with it as the open source solution, and thus contribute more
> developers to the Turbine community. However, since the Turbine
> developers also seem to know WebLogic, I would appreciate a candid
> assessment so I can make the right decision.
Well, having worked with Weblogic, it is an excellent piece of software. I
still wouldn't use it again if I could help it. JServ is a better solution
for me.
> P.S. If I get enough substantial feedback on this, I will be happy to
> create a feature matrix which makes clear the comparisons and which
> may assist in creating a roadmap for future Turbine development.
That would be awesome!
> BACKGROUND
Excellent!
>> Turbine is not a web application server. It is a tool for building web
>> applications.
>> Your servlet engine is your application server and the application that
>> you develop
>> using this framework is your web application.
>
> So I concluded that the combination of JServ+Turbine is an open-source
> alternative
> to BEA WebLogic's Application Server software.
No. Weblogic is a web application server. I'm saying that Turbine is NOT
that. It is like the MFC. For example, if you use Weblogic, you still have
to write the code that allows you to easily parse GET/POST/PATH_INFO into
something that is easy to retrieve. By using the classes that are available
in Turbine, you are essentially using re-usable code that others have
developed. How nice is that? ;-)
> So I was not sure whether the developers would in fact recommend WebLogic for
> those who could afford it.
I can afford it and I still wouldn't use it. Primarily for the OS reasons
mentioned above. I also got tired of trying to figure out why my software
wasn't working.
> Meanwhile, I did a good bit of research on available web application servers,
> and I thought this might be valuable to share with the Turbine community.
It would be GREAT if you added that to the FAQ...which also happens to be
powered by Turbine (eat your own dog food, right? ;-) )
<http://java.apache.org/jyve-faq/Turbine>
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
