Hello,

I've changed my config() proposal again, and have the latest draft here: 

http://mark.stosberg.com/perl/ca-standard-config-v4.html

I've tried to keep things really, really simple for all parties
involved, while still leaving room for expansion, and keeping the 
core free of any changes. 

If you want to view the source or patch the pod, it's here:
http://mark.stosberg.com/perl/ca-standard-config.pm

I'm most interested to hear from the three other config plugin authors
I've CC'ed besides myself. Are you willing to implement this standard? 

I've reviewed all the other plugin modules, and they can all implement
this and be backwards compatible. 

In some cases it won't be a consistent with the current interface. In
this case, you can document the standard compliance in fine print at the
bottom of the docs-- there is no need to indicate that you our config
plugin users needs to use the module any differently.

A final caveat: While I've thought about this design a lot, I haven't
actually tested it. I will do that with the ConfigAuto plugin once I
have some feedback.  For those who favor a different implementation, I'd
appreciate if you also put forth some formal docs and code as
alternative (as I have). 

Cees expressed interest off-list in having a config() method that
dispatches to several possible config backends. Something more complex
like that could be built on this standard because it could provide
a config() method that meets the standard. 

Although I've been thinking about this alot today, I do expect that many
you may be enjoying a more traditional holiday, and I won't expect much
feedback for a week or so as a result.

    Mark

-- 
http://mark.stosberg.com/ 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to