large web application

**Rob R. Ainscough** · Nov 22 '05, 05:52 PM

Re: large web application

"but at the same time I don't want to make an application that
requires constant changing to add features."

Being dynamic keeps one ahead of the competition -- so you might want to
build your app in such a way that adding features is as painless as
possible. The only constant in everything is CHANGE. :)

But I'd say you have the right tools for the job. For Web based processing,
my only advice is to keep the web site interface(s) as simple as possible --
90% of the web development work I've seen attempts to overload the user
interface (aka everything on a single page). Pay very close attention to
security -- I found the Microsoft press book "Building Secure Microsoft
ASP.NET Application" a great source.

"DKode" <dkode8@gmail.c om> wrote in message
news:1106875860 .074532.186870@ c13g2000cwb.goo glegroups.com.. .[color=blue]
> OK,
>
> so i'm designing a very large business auction website for a customer.
> It would include such features as: Auctions, search, registration,
> payment, fees on auctions, consignment services etc..
>
> I just started laying out the design for all the objects to create
> site, is there any advice anyone can give me when designing a website
> this large. I want to make sure I make development time as quick as
> possible, but at the same time I don't want to make an application that
> requires constant changing to add features.
>
> It will have a SQL server backend, asp.net using C# and be integrated
> with a merchant account and SSL certificates for secure credit card
> input etc..
>
> any advice would be greatly appreciated.
>
> Thanks!
>
> DKode
>[/color]

**Cor Ligthert** · Nov 22 '05, 05:52 PM

Re: large web application

DKode,

What are your goals different from other web applications, there should be
tons of books to help you.

Just my thought,

Cor

**Jim Douglas** · Nov 22 '05, 05:52 PM

Re: large web application

Hire someone that has does this before to help. Be sure this person was key
in the project from start to finish.

"DKode" <dkode8@gmail.c om> wrote in message
news:1106875860 .074532.186870@ c13g2000cwb.goo glegroups.com.. .[color=blue]
> OK,
>
> so i'm designing a very large business auction website for a customer.
> It would include such features as: Auctions, search, registration,
> payment, fees on auctions, consignment services etc..
>
> I just started laying out the design for all the objects to create
> site, is there any advice anyone can give me when designing a website
> this large. I want to make sure I make development time as quick as
> possible, but at the same time I don't want to make an application that
> requires constant changing to add features.
>
> It will have a SQL server backend, asp.net using C# and be integrated
> with a merchant account and SSL certificates for secure credit card
> input etc..
>
> any advice would be greatly appreciated.
>
> Thanks!
>
> DKode
>[/color]

**DKode** · Nov 22 '05, 05:53 PM

Re: large web application

I guess this isn't really that different from many other web
applications I've built. It's just that this project will have many
more add-ons than any other application I've created. Plus there are
many, many nuances such as fees, special acutions, consignment service,
forums, registration, administrator access to change the fees, payment
schedule, etc....

I started by writing everythign out in paragraphs for each process the
site will do, from reading a couple of UML books i'm trying to follow
the same patterns they have, then once I have all processes laid out I
will show the owner of the site to make sure I havent missed anything
and start creating the objects needed from there.

The way I viewed it is a normal 3-tier application. Database backend
broadcasting to a business layer that will in turn broadcast
datasets/datareaders to the web frontend.

any other opionions on the use of datasets? I imagine on some of the
database requests that the sql query would return a very large number
of rows, in which case I would use datareaders as often as possible.
thanks!

**Cor Ligthert** · Nov 22 '05, 05:53 PM

Re: large web application

DKode,

This sentence triggered me.
[color=blue]
>I would use datareaders as often as possible thanks![/color]

When there is only "reading" there is seldom a problem in a design, in my
opinion is setting your view on "updating" in a multiuser environment a
better approach. You said "Auctions" and therefore even more.

Just an idea that came up by me reading your message.

Cor

**DKode** · Nov 22 '05, 05:53 PM

Re: large web application

thank you

that helps me focus on certain areas more than others and pay close
attention to the updating of data. I know that datasets incur more
overhead that using a datareader and creating the update code myself.

I don't think I want to manage all the updating myself and it would be
easier to use datasets, but I forsee that often I will only be updating
one row at a time and/or inserting a new row in another table.

in opionion, for stuff like this would I be better off with datasets or
homegrown data updating techniques?

thank you.

DKode

**Cor Ligthert** · Nov 22 '05, 05:54 PM

Re: large web application

DKode
[color=blue]
> in opionion, for stuff like this would I be better off with datasets or
> homegrown data updating techniques?
>[/color]
Here I cannot give you an advise I am in doubt myself in the benefit of the
classic 3 tier in ADONET so this I leave to others.

Basicly a webapplication with a DLL created by VSNet in Net is
UI(the browser)<->The Application which is for all clients<->The database

As you see a 3 tier

I hope this gives some idea's anyway?

Cor

**DKode** · Nov 22 '05, 05:54 PM

Re: large web application

yeah, that helps. I pretty much have an overall idea of 3 tier as I
have designed 3 tier apps b4.

thanks!

large web application

large web application

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment