Re: when to break up a large application?
Re: when to break up a large application?
- Subject: Re: when to break up a large application?
- From: steve stout <email@hidden>
- Date: Thu, 29 Jul 2004 21:34:16 -0700
The question is not so much when to break it up into multiple
applications, it's when to break it up into multiple frameworks with a
small application on the front end. It's a good thing to use frameworks
to organize and reuse code. In the case of the Apple Store, I would
suspect that 99% of the code and components are contained in multiple
common frameworks and each front end application just customizes the
front page and what db to look at for the items displayed. Also, I'm
sure they're separate apps because they want to make sure that a user
doesn't figure out how to put an item from the US store in their cart
and then go to the Japan side and check out there.
You may need to break it up into multiple applications if it makes
sense to actually have it in a different application. Just like iTunes
and iPhoto are 2 different applications and .Mac and the Apple Store
are 2 different applications, make sure you're not creating an app
that's too monolithic. But breaking it up into multiple apps creates
problems when it comes to keeping a user's session and handing off the
user from one app to the other. Just do what makes sense.
.steve
On Jul 29, 2004, at 8:57 PM, William Norris wrote:
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.
_______________________________________________
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.