Jochem and Michael,
Interesting ideas - thanks!
I think I have done a poor job of describing the scenario. Ben Forta's
"Maybe We Should Try a Separation" (CFDJ Vol 4 Issue 10) really got me
to thinking: there are so many good reasons for code reuse (faster
development time, centralized ("policable") code, easier debugging,
etc.) But getting developers to tie into existing resources is
hopeless, particularly when your community of developers comes and goes
and is rarely around long enough to really respond to your efforts to
get them to reuse codes and build off each others' functionality.
So forget about my scattered scenario and emphasis on databases: just
consider this question: How could you set up a server architecture
(whether internally via security sandboxes or externally via web service
syndication servers) that would encourage a development culture whose
members were free to develop however whatever they wanted, but faced
strong incentives to first utilize each others' reusable code?
Remember two things:
First, the community we are considering suffers from frequent turn
around. Some of its members are pretty clever - most just want to get
something up and aren't always that interested in looking under the
hood.
Second, Their needs in functionality are generally pretty uniform. Sure
they have their own data and different presentation layers. But they
all have the same basic "poll", "announcements", "staff directory" kinds
of features on their website.
In other words, one good developer could probably do 95% of all the
functionality they need.
So how best to not merely advertise what that developer has done, but go
further and place strong incentives in their development methodology to
consider tying first into that developers' components and other
extensions?
Seems to me the best way would be to put everyone in one sandbox denied
certain tags and ports, etc... but let them all post, per your
developers' approval, concise reusable code into another sandbox without
restrictions.
Think of the implications for users both novice and advanced, for the
administrators' responsibility to ensure a secure and available
environment!
-Jason
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2003 8:35 AM
To: CF-Talk
Subject: Re: An ISP's Dream: Extensions in one sandbox, client code in
another
Michael T. Tangorre wrote:
> Just plan for it... have two databases running on
> a server so when one is mangled you can switch to the other one and
vice
> versa.... Now in a real world situation, resources are limited to some
> extent or should be anyway.
We have long since adopted the position that it is easier to just
buy extra harddisks as to set, maintain, measure and enforce
quota on disk use, bandwidth use and databases :-)
(If university provides you with a bunch of switch ports and
power plugs for free, business rules change quite a lot.)
Jochem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
http://www.cfhosting.com
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
