Re: Methodology conflicts. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Methodology conflicts.
From: Scott Klement <klemscot@xxxxxxxxxxxx>
Date: Wed, 6 Nov 2002 18:07:46 -0600 (CST)
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I think you mean 'stateless' programming, such as something in a web
browser, rather than event-driven programming.

If so, I agree...


On Wed, 6 Nov 2002, Booth Martin wrote:
>
>  Isn't that difference between cycle-driven and event-driven?  Event-driven
> programming requires immediate processing of data because one never knows
> whither goest the user.
>
> My experience so far says event-driven is a good thing.  Opens up so many
> more choices for the programmer.
>

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.