aspect of it seems only suitable for intranets. I see the reasoning
for the abstraction, but I feel that the way they've gone about it,
making the vb programmers feel at home, results in some really kludgy
ways of doing things.
The VB guy where I work is trying to transition to web work. He's
having a hard time figuring out when code runs on the server and when
it runs on the client side. He's also having a hard time getting out
of the client/server frame of mind.
He made a security module today where he stored the username and
password in 2 global variables. You should have seen his face when I
"logged into" his application as him without ever supplying
credentials.
This is the danger of abstracting too much.
Marlon
On Fri, 25 Jun 2004 14:58:28 -0400, Dave Watts <[EMAIL PROTECTED]> wrote:
> I kind of feel the same way sometimes; I'd often rather have direct control
> over the HTML I'm generating. However, there's a very good reason for
> abstracting this into the control itself. You can easily have controls that
> generate environment-specific code, without having to actually rewrite your
> own code. For example, you can use the ASP.NET Mobile Controls, which will
> generate WML for some platforms and HTML for others. JavaServer Faces is a
> similar idea, I think, although I haven't worked with that directly.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> phone: 202-797-5496
> fax: 202-797-5444
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
