RE: Database Maintenance Models

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Nathan Andelin
> 
> Wouldn't the topic
> of UI design patterns be appropriate on ANY developer list?

No, the general discussions of the pros and cons of language-agnostic
patterns is more at home either on an architecture list (which I don't
believe really exists on midrange.com) or at the new web site.


> I've had the means of implementing program "skeletons" as you call
them
> for
> several years, but lacked a UI design patterns that anyone besides
myself
> could agree with.  More recently, I've been working with a UI design
team
> that has come up with a more comprehensive model, which I thought
might be
> of interest to readers here.

I agree that pure models might be of benefit to any programming
community, and particularly an OO based community, which theoretically
has the tools to derive working code from UML models.  So if you have
modeled this using any of the standard modeling tools, I think the
resulting UML would be a great addition to the discussion.

If you're going to talk about models, I think it's appropriate to use
the industry standard terms.  Otherwise, it's just code generation all
over again, and that's where we run into problems.


> > See, you're already narrowing down the look and feel
> > to your specific UI requirements.
> 
> Precisely.

So you've got a non-Java, non-servlet technique that builds a specific
set of HTML based on your business requirements.  That makes it
inappropriate to this list, but perfectly suited for the new web site.


> In the case of Servlets, using a meta-data driven utility has the
added
> concern of scalability.  Say there are hundreds of users maintaining
> hundreds of files.  Wouldn't channeling every request through one
Servlet
> offer a substantial bottleneck?

Servlets are multi-threaded.  That's the whole idea. THIS is the sort of
question that's appropriate on this list.

Joe Pluta