Good to see you've already thought these things through. Thanks!
On 10/20/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
We're thinking on the same frequencies here. If you check the new screencast (#2) and documentation, you'll see that DataSqueezer is out. A typical URL might be: http://localhost:8080/Start.action/choose/10 The context parameter of ActionLink (equivalent to DirectLink's parameters parameter) is an object, or list of objects, added to the URL. It's just basic toString() for them, none of the wacky prefixes. On the flip side, the event handler methods also use TypeCoercer to convert the strings back to objects or (more often) primitives. If you want to do something like DataSqueezer, but in Tapestry 5, you're on your own; you'll have to convert your object to a string and back. Not so onerous, given how pervasive service injection is. To be honest, I don't think it will be necessary. All I've seen is people getting in trouble trying to serialize large object graphs into the URL. It'll be now much more evident that you should store the object ids, not the objects themselves. This represents one of the many simplifications of the framework that work in everyone's best interest. We're venturing towards the Principle of Least Surprise. On 10/20/06, D&J Gredler <[EMAIL PROTECTED]> wrote: > > Hi, > > Just wanted to get this out there and possibly on Howard's radar screen... > > It would be nice if the new Tap5 type coercion framework (used with > component parameters) could also be used with link parameters, so as to > avoid the single-character type prefixes that make Tap4 URLs > almost-friendly-but-not-quite-there. I'm talking mainly about ExternalLink > or whatever the Tap5 functional equivalent is. > > Take care, > > Daniel > > -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
