On Fri, 04 Nov 2011 00:40:08 +0100, Marco Faustinelli
<[email protected]> wrote:
Jan,
I am afraid that going from discarding Vaadin because of its un-
ability to manage 100k points on the server to ending up excited about
a sketching tool that produces PDF, JPG or proprietary XML does not
testify of a clear decision-making path :-)
Exactly. My point is: either you have a HTML5 solution capable to comply
with the specs, and - for some reason - it's not compatible with Vaadin
(or it fully provides all the things that Vaadin does), so it's legit to
exclude Vaadin; or you have a Flash/Flex/Java/C#/Whatever solution that
handles the 100k (and it seems this is the way), and for sure it can be
integrated with Vaadin. And keep Vaadin for all the other good things.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
