While that is true.. It's also true that wicket devs favor stuff proven
with a quickstart, because it becomes easier to make a fix for something
you can see in code..
So as I've written once before a quickstart should be the way to go or
just use one of the existing applications, phone book or blog tutorial
etc. And make a hack at that...
regards Nino
Ned Collyer wrote:
Nick, I think you would be quite surprised at the level of auditing something
has to pass to be used in a financial system, especially a bank. (unless u
have some dodgy bank)
If something is theoretically possible, then thats as good as "proven".
Gotta remember that hackers are a lot smarter in many instances than the
people who wrote the software to keep them out.
Nick Heudecker wrote:
Arthur,
Only what you can *prove* matters, not what you think. Have you created
an
example application with a CSRF attack?
--
-Wicket for love
-Jme for fun
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
