when to break up a large application?
when to break up a large application?
- Subject: when to break up a large application?
- From: William Norris <email@hidden>
- Date: Thu, 29 Jul 2004 22:57:12 -0500
I'm wondering if there are any conventions that other developers
follow when it comes to breaking up a large application into multiple
smaller ones. Of course I know it differs for each individual
application, but I'm wondering at what point does an application seem
too large? When you are being overwhelmed with Components? (how many?
hundreds? thousands?)
I noticed Apple uses a seperate application for their store based on
country (http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa
[vs] http://store.apple.com/1-800-MY-APPLE/WebObjects/canadastore)
though I'm sure there are many Components shared between the two.
However, one must wonder why they develop seperate WO Apps, when the
primary difference is probably price and perhaps availability.
looking for some insight into best coding pracices,
Will
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.