> > If you have a structure. A->C, B->C then you might actually > > want back functionality. Otherwise you have to create two > > copies of C (A<-C1, B<-C2) > This makes no sense to me whatsoever. You don't need more > than one copy of C at all, just keep referencing C from > wherever you call it. This is how the web works. I don't see > why you need to duplicate information just to link to it from > two different places.
Okay, I've got two pages, A, and B. Both have a link to C. I want to put a "Back" link on C. Which page does it point to? > > However, some functionality, like client-side form > > validation, is nice to have, though. > ..and incredibly easy to exploit. I'd love to see a list > of sites that are still using this antiquated approach to > insecure form validation. I used to use client-side form validation _all_ the time. Not as a replacement for server-side validation, but as a way to short-cut most of the errors the client might get, since it's a lot faster than having to make yet another connection to the server to find out what's wrong. > Yes, and some are blatently violating the GPL with it > too, still an open issue with the core Plucker team, > and one which should be resolved soon. Oooh! This sounds like a teaser for some good news. I can't wait. > > In the interest of fairness you should mention that AvantGo > > has a dedicated conduit, while Plucker does not. It is still > > easier to use for ordinary users. What do you mean by a "dedicated conduit"? Plucker has had a (Win32) conduit for quite a while now. > it still tethers your Palm to the cradle until the entire > content is fetched and delivered, something Plucker does > not do, thankfully. And that's why I uninstalled the Plucker conduit a week after installing it. :) > I think the goal, along with replacing simple things like > this, should be to educate content providers to fix their > pages to be compliant with the HTML specification, and other > ways to increase their readership. I've had quite a bit of > good luck doing this in the past few years. Some tell me to > pound sand, and others actually work with me to clean up > their pages. I think that the goal should be to produce a browser that handles as many things as it can without becoming too slow. (I've found that asking people to fix their pages has been almost as useful as pounding sand, and so would rather have a client that's liberal in what it accepts, and does its best to render whatever crap it's given.) Of course, this is the beauty of Open Source. People can submit patches to drive the product in the direction they want it to go. Later, Blake. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
