Re: .Net (Was: Re: suggestions please)
by "Frank Boumphrey" <bckman(at)ix.netcom.com>
|
| Date: |
Sat, 1 Dec 2001 01:11:26 -0500 |
| To: |
<kathyw(at)home.albury.net.au>, <hwg-techniques(at)hwg.org> |
| References: |
yahoo chartermi D1C4FN01 kathydell |
| |
todo: View
Thread,
Original
|
|
> Well golly-gee, don't mean to sound trite Frank but I've been doing that
with
> PHP for ages ... it's hardly a new concept
Yes,
this is easy enough to do (with PHP, ASP, JSP, PERL, you name it) with a
simple page and a relativly small infosetation, but when you are talking
about a recordset of say 1000+ records, the problem becomes apparent.
Maintaining state with custom programming soon becomes an overwhelming
task!!
.NET trivalises and makes transparent this process.
Frank
----- Original Message -----
From: "Kathy Wheeler" <kathyw(at)home.albury.net.au>
To: <hwg-techniques(at)hwg.org>
Sent: Friday, November 30, 2001 10:38 PM
Subject: Re: .Net (Was: Re: suggestions please)
> I don't agree with the term "advantage" unless you mean advantage to
> Microsoft.
>
> > 1.They do away with scripting and interpreted pages. In fact the first
time
> > the pages run (by the developer) they are compiled to a dll. on the
server.
>
> Designed most probably to tie developers into Microsoft's operating
systems
> and Servers?? That would be a serious concern, especially in light of
> Microsoft's proven illegal tactics in previous promotion of it's operating
> systems. I can smell another anti-trust case in the wind.
>
> > 2. The second advantage is that state is maintained on the client side,
not
> > by a cookie, but by a value in a hidden input element passed to the
page.
>
> Well golly-gee, don't mean to sound trite Frank but I've been doing that
with
> PHP for ages ... it's hardly a new concept.
>
> KathyW.
HWG hwg-techniques mailing list archives,
maintained by Webmasters @ IWA
This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.