Re: [Web-SIG] Standardized template API

2006-02-01 Thread Phillip J. Eby
At 12:12 PM 2/1/2006 -0500, Michael Bayer wrote: On Feb 1, 2006, at 11:07 AM, Phillip J. Eby wrote: spec is about (like what is template polymorphism exactly ?) Specifying only a template's *name* in code, not its type. In peak.web, if I refer to a resource or template named foo, the system

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Phillip J. Eby
At 11:43 AM 2/1/2006 -0500, Clark C. Evans wrote: On Tue, Jan 31, 2006 at 08:55:22PM -0500, Phillip J. Eby wrote: | Indeed, I'd argue that it'd be better here to create a WSGI-based | template interface, rather than a specialized template interface. | That is, if the compiled template returned by

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Michael Bayer
On Feb 1, 2006, at 12:59 PM, Phillip J. Eby wrote: At 1 So asking for foo can resolve to foo.gif or foo.jpeg in the file system? If you have to say in the code which it is, that's not what I mean. you can write a resolver that searches the filesystem for foo.* and does some type

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Chris McDonough
One specific concern about the returning the published object for publisher-based frameworks is that often the published object has references to other objects that might not make sense in the context of the thread handling the rendering of the template. For example, if you're using a

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Ian Bicking
Phillip J. Eby wrote: My criteria is that it would be easy to implement Phillip's proposal in terms of mine (and I could provide a sample implementation of that if it would help), but it doesn't seem so easy to do the opposite. Actually, I believe you've got that backwards. Many things

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Clark C. Evans
On Wed, Feb 01, 2006 at 05:15:26PM -0500, Phillip J. Eby wrote: | The template doesn't get to control the status or headers if all it | can do is return is a string. WSGI the hammer! Must we necessarly have a nail here? I think what's missing in this discussion is that templates are often used

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Phillip J. Eby
At 05:42 PM 2/1/2006 -0500, Clark C. Evans wrote: | The template doesn't get to control the status or headers if all it | can do is return is a string. WSGI the hammer! Must we necessarly have a nail here? Who's we? Strings don't meet *my* use cases, or those of other template system and

Re: [Web-SIG] Standardized template API

2006-02-01 Thread Rene Dudfield
On 2/2/06, Phillip J. Eby [EMAIL PROTECTED] wrote: C'mon guys, where's the shooting down of my ideas that y'all promised? ;) Bang. ___ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: