tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Smith <david.sm...@cornell.edu>
Subject Re: How to convert WAR application into console application (Making Unicorn has console application)
Date Fri, 20 Aug 2010 15:45:09 GMT

> I tend to agree.  All this graphical stuff is making life miserable for most of us web

> developers.  Back before Tim Berners-Lee came up with HTTP and HTML and made things 
> horribly complicated, one could still concentrate on the quintessential meaning of things,

> rather than spending most of one's time with presentation matters, users clicking all
over 
> the place, multiple threads, connection pools and whatnot.

This is what the MVC pattern is all about.  The model get's implemented
in it's own jar and has it's own development lifecycle to handle the
backend business logic.  As long as it's designed not to have anything
to do with the front-end, life is good whether it be in a console java
app or a servlet container w/ an html front-end.

--David


On 8/20/2010 11:30 AM, André Warnier wrote:
> Caldarale, Charles R wrote:
>>> From: Ranjith [mailto:ranjith.k@sedin.co.in]
>>> Subject: Re: How to convert WAR application into console application
>>> (Making Unicorn has console application)
>>>
>>> No Its working fine but i want to execute it on console that 
>>> is my project.
>> Let me see if I understand this correctly:
>>
>> You're asking a Tomcat support mailing list about how not to use Tomcat?
>>
> I think you've got this wrong.  The OP just wants to create a console version of the

> application.
>
> I tend to agree.  All this graphical stuff is making life miserable for most of us web

> developers.  Back before Tim Berners-Lee came up with HTTP and HTML and made things 
> horribly complicated, one could still concentrate on the quintessential meaning of things,

> rather than spending most of one's time with presentation matters, users clicking all
over 
> the place, multiple threads, connection pools and whatnot.
>
> I applaud the OP's project, and would refer him for example to RFC 1436, describing the

> Gopher protocol.  The quintessential elegance and simplicity of this protocol is 
> demonstrated by the following summary, extracted from the Introduction of said document
:
>
> Quote
>
> Users run client software on their desktop systems, connecting to a server and sending
the 
> server a selector (a line of text, which may be empty) via a TCP connection at a well-

> known port.  The server responds with a block of text terminated by a period on a line
by 
> itself and closes the connection.  No state is retained by the server.
>
> Unquote
>
> Isn't this beautiful ?
> How many centuries of unproductive programming time, and how many petabytes of RAM and

> disk would have been saved, if the professional IT world had just stuck to the simple

> principles outlined above, rather than falling for all these hyper- metaphors ?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message