|
Loading...
|
tapestry-dev@jakarta.apache.org
[Prev] Thread [Next] | [Prev] Date [Next]
Re: Tapestry 3.1 status David Solis Thu Sep 09 09:30:44 2004
On Tue, 7 Sep 2004 17:33:53 -0400, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Engine services are going to change a lot. > > The <service> element in app/library spec will be decprated, possibly > ignored, in favor of HiveMind. > Isn't the same case for some extensions, for example Monitor? > Constructing a ILink (a combination of a URL and query parameters) is > going to be much more complex. > > In addition, many pesistent page properties are going to persist on > the client as query parameters (hidden fields in a form, or additional > qp's in any generated ILinks). So there's going to need to be a lot of > collaboration around the system that isn't practical with the 3.0 > infrastructure. > This is a good idea. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- Re: Tapestry 3.1 status, (continued)
- Re: Tapestry 3.1 status Glen Stampoultzis 2004/09/06
- Re: Tapestry 3.1 status Howard Lewis Ship 2004/09/07
- Re: Tapestry 3.1 status Glen Stampoultzis 2004/09/13
- Re: Tapestry 3.1 status Robert Zeigler 2004/09/13
- Re: Tapestry 3.1 status Glen Stampoultzis 2004/09/14
- Re: Tapestry 3.1 status Robert Zeigler 2004/09/14
Re: Tapestry 3.1 status Paul Ferraro 2004/09/07
- Re: Tapestry 3.1 status Howard Lewis Ship 2004/09/07
- Re: Tapestry 3.1 status Howard Lewis Ship 2004/09/07
- Re: Tapestry 3.1 status Erik Hatcher 2004/09/08
- Re: Tapestry 3.1 status David Solis 2004/09/09 <=