I can see your point, but given that you don't want just anyone posting to your blog and given that LOTS of CF application (I would be a majority) have some kind of back-end functionality that is protected at some level with a username/password that some minimal level of user authentication/authorization will be necessary to feel like the app is "complete" -- the nice thing about a blog is that it's a fairly discrete set of functionality that everyone on this list is probably familiar with.
One big question -- is it an app that runs one blog, or an app that can run any number of blogs? For the sake of keeping things simple, I'd suggest it be for running one blog. I would also like to suggest that the application should have the capability to deploy on a shared server where you cannot make assumptions about where the CF root is (though, CF mappings may be fair game in that scenario). If that is not an acceptable criteria to everyone participating, I'd suggest one of the "teams" focus on making this a priority. I also wonder if it might be good to divide up the project priorities -- to have one application built with scalability as the primary concern while another has ease of deployment as the primary concern while another has extensibility as the primary concern, etc.?? Do y'all foresee having team "leaders" who architect a system and then have "teams" who implement? Or, would you rather just folks interested build their own and see what happens? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Brian LeRoux > Sent: Monday, March 31, 2003 4:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] bakeoff > > > I'm all about exploring application frameworks but a security is a > massive squirming can of worms and walks waaaay outside the scope of > this exercise. If the framework is sound plugging this kind of > functionality should be simple. Same with error trapping. > > Just my thoughts - brian > > > > > I think that will vary for each style of implementation. > > Rather than having everyone need to use the same XML/data > > format, I suggest the requirement simply be the persistence > > should be pluggable -- perhaps with an agreed upon API (or, > > at least, a single API for each "baked dish"). > > > > In addition to the functionality of the blog itself, I think > > this exercise would benefit from explicitly creating some > > modular (as in, reusable) functionality for common > > application functions like: > > > > 1) User Authentication/Authorization (for the back-end) -- > > perhaps agreeing there are two "user types" ("god" users and > > content publishers, perhaps) > > > > 2) Form/Data validation and the resulting error/notification > > messages showed to the user. > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Behalf Of Benjamin S. Rogers > > > Sent: Monday, March 31, 2003 4:34 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [CFCDev] bakeoff > > > > > > > > > By that, do you mean XML? If so, would you like to propose a file > > > structure? > > > > > > Benjamin S. Rogers > > > http://www.c4.net/ > > > v.508.240.0051 > > > f.508.240.0057 > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > > Behalf Of Bryan F. Hogan > > > Sent: Monday, March 31, 2003 7:23 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [CFCDev] bakeoff > > > > > > > > > Ok, I jumped in late. I'm on the same page now. > > > > > > Here is my 2: > > > > > > The storage mechanism should be file based. > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Behalf Of Matt Liotta > > > Sent: Monday, March 31, 2003 7:19 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [CFCDev] bakeoff > > > > > > > > > I don't have a timeframe and I thought we were just working on the > > > list of requirements. > > > > > > Matt Liotta > > > President & CEO > > > Montara Software, Inc. > > > http://www.montarasoftware.com/ > > > 888-408-0900 x901 > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > > Behalf > > > > Of Bryan F. Hogan > > > > Sent: Monday, March 31, 2003 7:13 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: RE: [CFCDev] bakeoff > > > > > > > > Is there a timeframe? Do you have a list of requirements > > available. > > > > > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > > Behalf Of Matt Liotta > > > > Sent: Monday, March 31, 2003 6:52 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: RE: [CFCDev] bakeoff > > > > > > > > > > > > > I think the RSS feed(s) could be produced using presentation > > > templates > > > > > rather than a separate mechanism. > > > > > > > > > That is what I meant actually; sorry for the confusion. > > > > > > > > > Also the ability to turn comments on/off for a > > particular post or > > > > > to > > > > close > > > > > comments off. > > > > > * Add/edit/delete comments > > > > > > > > > Good point! > > > > > > > > > Also (this might be a bit much) > > > > > * A bulk entry import/export mechanism > > > > > > > > > Agreed on the bit much. > > > > > > > > > The production of dynamic pages (over writing html files) is > > > > preferable > > > > > given our aim, though from an application perspective, producing > > > > static > > > > > pages has a number of advantages. > > > > > > > > > Indeed it would be preferable for our bakeoff. > > > > > > > > -Matt > > > > > > > > > > ---------------------------------------------------------- > > You are subscribed to cfcdev. To unsubscribe, send an email > > to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' > > in the message of the email. > > > > CFCDev is run by CFCZone (www.cfczone.org) and supported > > by Mindtool, Corporation (www.mindtool.com). > > > > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' > in the message of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported > by Mindtool, Corporation (www.mindtool.com). > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
