Just to followup, I setup a Google Code site as a place to describe and design cross-platform technologies that pertain to web application development and deployment. For some time now, I've spent half my time working in .NET, which probably won't change for another year or two, and so working on cross-platform technologies is of great interest to me.
I've extended the initial draft posted here to include the action URI to Action Class mappings. While based on SmartURLs and CodeBehind, the description goes beyond what either can do right now. * http://code.google.com/p/web-alignment-group/wiki/WAG_RFC_001 Before doing any more work on the description, I'd be very interested on feedback as to whether I'm making any sense, or whether the draft has turned into opaque gibberish :) -Ted. On Oct 17, 2007 2:24 AM, Ted Husted <[EMAIL PROTECTED]> wrote: > Following up on suggestions made by Don and Brian, I'd like to propose > that we draft a formal specification describing the logic to be used > by the (deep-breath) "Able/Code Behind/Zero-Config/SmartURLs" plugin > for 2.1. The purpose of the specification would be to better define > what "backward compatibility" means, and also to encourage > implementation of this pattern by other frameworks. > > Following is the beginning of an early draft of a proposed > "view-behind" specification. (In case anyone is interested, I'm using > the JSON-RPC specification format as a model.) If there is interest in > this proposal, I'd suggest we decide whether to complete the > specification as part of our documentation, or at some other location. > Of course, people working with other frameworks > (<cough>stripes</cough>) would be welcome to join in. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
