[ale] need your input on a project...

[Denny Chambers]

Enhydra.com did go belly up. Enhydra also had a bunch of open source 
projects that are now hosted by ObjectWeb. I can't speak for the other 
projects, but Barracuda, and XMLC are both still in development. I have 
been working on the Barracuda stuff for a while now, and have submitted 
some patches my self. To help make sure that failing companies like 
Enhydra don't upset the good development going on there, they 
(Barracuda) are in the process of getting there own website, and server 
up. They have purchased the domain (barracudamvc.org), the server, and 
have an ISP that is willing to donate the bandwidth. So a new server 
should be up soon.

Denny

Matthew Brown wrote:

>I looked close at the enhydra stuff.  First, they look like top-notch
>developers.  BUT, they just went belly-up several months ago, and who
>knows how well ObjectWeb will do at taking it up?
>
>Best regards,
>Matthew Brown, President
>CorData, Inc.
>O: (770) 795-0089
>F: (404) 806-4855
>E: matthew.brown at cordata.net
>
>
>-----Original Message-----
>From: Denny Chambers [mailto:dchambers at snapserver.com] 
>Sent: Friday, October 18, 2002 3:51 PM
>To: John Wells
>Cc: ale at ale.org
>Subject: Re: [ale] need your input on a project...
>
>
>I am currently working on a rather large Servlet based application 
>myself. When finished, it will be about 80-100 screen. We have been 
>using Tomcat/Linux/JDK 1.4.1 with no problems so far. We also use a Web 
>Application framework from Enhydra called Barracuda 
>(barracuda.enhydra.org). We also use another tool called XMLC which 
>compliments the Barracuda framework. Using Barracuda helps to give you a
>
>clean separation of your UI logic from your back-end logic, something 
>traditional CGI, Servlet and JSP/ASP approaches do not give you.. This 
>really helps with maintainability.
>
>HTH,
>
>Denny
>
>John Wells wrote:
>
>  
>
>>Guys,
>>
>>Just landed a rather large project involving converting a VB/Access/Sql
>>Server app to an open source app.
>>
>>I'm most likely going the web approach because it makes very good sense
>>    
>>
>in
>  
>
>>this case.
>>
>>However, this is where I'm a bit indecisive.  I've used PHP quite a bit
>>    
>>
>in
>  
>
>>the past, and while it's very nice for smaller projects, I think it
>>    
>>
>tends
>  
>
>>to get messy as the project grows.  This particular app will have over
>>    
>>
>70
>  
>
>>screens and a lot of background processing, so I'm not convinced PHP is
>>the way to go.  I also want to go OO, and although PHP has limited OO
>>capabilities, it begins to feel a little Perl-y after a while
>>(<flamebait>granted, PHP's OO syntax is much cleaner than
>>Perl's</flamebait>).
>>
>>My next thought was: Gee...wish Python web programming was really
>>    
>>
>*There*.
>  
>
>>I looked at web programming in python briefly in the past, and it
>>    
>>
>seems
>  
>
>>as if there was either A. cgi scripting,  or B. a number of server
>>pages-like projects, but cgi is not the way I'd like to go for
>>efficiency's sake, and the server page projects looked to be a little
>>beta-ish and not what I need for a project of this magnitude.  Then
>>there's Zope, which seems mature, but folks have mentioned problems
>>    
>>
>with
>  
>
>>threading and the like.
>>
>>So, finally, my last option is Java/Jsp/Servlets.  I have a lot of
>>experience in this area, so coding wouldn't be a problem.  However,
>>    
>>
>iirc
>  
>
>>Tomcat is not really intended for production, so I'm not sure what sort
>>    
>>
>of
>  
>
>>servlet/jsp containers are available (and mature) as open source.
>>
>>Ultimately, I need something clean and fast, with a fairly good support
>>community.
>>
>>Any thoughts?
>>
>>Thanks for your input.  It will be greatly appreciated.
>>
>>John
>>
>>
>>
>>---
>>This message has been sent through the ALE general discussion list.
>>See http://www.ale.org/mailing-lists.shtml for more info. Problems
>>    
>>
>should be 
>  
>
>>sent to listmaster at ale dot org.
>>
>> 
>>
>>    
>>
>
>
>---
>This message has been sent through the ALE general discussion list.
>See http://www.ale.org/mailing-lists.shtml for more info. Problems
>should be 
>sent to listmaster at ale dot org.
>
>
>
>---
>This message has been sent through the ALE general discussion list.
>See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
>sent to listmaster at ale dot org.
>  
>


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.