[thesite] My Intro and a look at a UEUE Proposal

Daniel J. Cody djc at starkmedia.com
Tue Oct 16 11:19:33 CDT 2001


Joshua Olson wrote:


> Sorry about missing CodeFest... I really wanted to participate in some form
> or fashion.  But, duty called.


no prob, we understand.. next time hopefully!


> A couple of factors are turn-offs for system replacement:

[snip]

all valid points..


> I know this is not a popular view amongst some people here, but I just want
> to know other people's thoughts.  Does anyone think a redo *might* be down
> the road?


um. :) its somewhere down the road, where exactly I have no clue..


> What sort of hang-ups might be present if we retrofit the system with
> changes if we stay with the current distributed db model?


the distributed DB model really stunts the ability of evolt to scale.. 
if someone wants to do a kickass project for evolt(like Simon did with 
d.e.o) without making it a pain in the ass on users, they have to get 
our user records somehow. also, replication of the entire DB is a 
serious bitch. :)

 
> What problems does this create?
> 1) a black box would have to be written for each engine -- CF, PHP, etc --
> that is powering a *.evolt.org site so that the user information can
> successfully be stuffed into session variables. This would suck if we didn't
> get it right the first time since any changes would have to be propagated to
> each code base.


again, what mark and i are talking about doesn't use sessions as the 
backbone of the system, and *thats* why we can get away with multiple 
application languages using it.

the login.evolt.org thing I tried a while back would easily work if we 
had every *.e.o site running Cold Fusion since session mangament within 
an app language is easy. but we shouldn't stunt the growth of cool 
projects or peoples willingness to contribute just because they don't 
know CF....

thanks for asking all these questions josh.. i'm sure others are 
thinking them too :)

.djc.

 






More information about the thesite mailing list