Hi all, I've been following the list from the start and I'd like to throw my $.02 cents in about that I want out of p5ee. I am a relative newbie compared to most folks on this list, but having done web apps for 5 years I've realized there are some things I'm tired of reinventing w/ each employer or contract job.
First and foremost, I want an API. This should handle messaging, sessions, persistence, and a whole bunch of other things I've forgotten or never yet used. At this point, the API is the important part. Since we're starting from scratch, we are presented with the opportunity to "Do the Right Thing", unhindered by existing code bases and assumptions. Proper design is essential to the success of p5ee. There are a lot of gurus on this list who I'm sure can come up with a good, generic API. And more importantly, one that can have various implementations plugged in w/ minimal effort. From what I can tell, the whole reason this project was even started was because of j2ee, and it's associated STANDARDIZED APIs. I can't debate the merits of said standards, because I am not qualified to do so. However, a java programmer who knows j2ee can go from Java shop to Java shop, and if they are using a J2EE container the learning curve is greatly reduced. This is the advantage. Let's not lose sight of this fact. I think perl programmers should have the same advantage. The API is the key. Given enough time, even I could code up modules that conform to a given API. But if I had to come up w/ said design on my own, I would probably fail. I guess my point is that I don't want this group to become too bogged down in details right now. IMHO, we need to focus more on the design, rather than the implementation. Let's (and I use this in the royal sense :-) use the newly received CVS access to put together our respective ideas for the APIs. The great thing is that once we have many people working on various aspects, we can then pick and choose what is included in the "base" distribution, and what would be "extensions". It's far too early to be writing any code, although it seems to me we're headed that way. If I'm wrong, please correct me. I have greatly enjoyed the threads so far on this list and learned a lot about what makes a "good" design good. Of course, I welcome all comments and/or flames. </me returns to lurk mode and puts on flame retardant underwear> Drew Taylor JA[P|m_p|SQL]H http://www.drewtaylor.com/ Just Another Perl|mod_perl|SQL Hacker mailto:[EMAIL PROTECTED] *** God bless America! *** ICQ: 135298242
