So I played with Vaadin a little bit - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Java - 爪哇娇娃

So I played with Vaadin a little bit

So I played with Vaadin a little bit# Java - 爪哇娇娃

m*t2010-04-23 07:04

1 楼

The out of box experience was impressive. I like the easy and
straightforward paradigm, which makes it possible to spend
most of the time actually implementing features, instead of
learning the tool. And the ability to implement logic in
full java capabilities (vs. GWT's watered-down subset) is
incredibly satisfying.
The big concern though is that the price we pay for all the
good things above is to do everything on the server. The UI
isn't going to be very snappy due to network latency. No
matt

g*g2010-04-23 07:04

2 楼

It's not going to be as fast as pure client side framework,
and it never will.
But you are still only updating a portion of the page at
a time. So called AJAX. The generation of that portion is
done on server side, I think it's going to be faster than
request-based frameworks where the entire page is sent over
the wire.
The other drawback would be memory consumption in the session.
Overall it's still very Swing and certainly fits a lot of
projects.

【在 m******t 的大作中提到】

: The out of box experience was impressive. I like the easy and
: straightforward paradigm, which makes it possible to spend
: most of the time actually implementing features, instead of
: learning the tool. And the ability to implement logic in
: full java capabilities (vs. GWT's watered-down subset) is
: incredibly satisfying.
: The big concern though is that the price we pay for all the
: good things above is to do everything on the server. The UI
: isn't going to be very snappy due to network latency. No
: matt

m*t2010-04-23 07:04

3 楼

Well, from a user's point of view, the response time of
a mouse click or key stroke has little to do with the amount
of page updates. That's _especially_ true for ajax
applications because the user is already used to incredibly
fast partial page updates.
I click on a check box, if it takes more than maybe
a second for that optional field to show up, that's not
feeling very responsive. If the user and the server are
on different coasts or continents, the network latency
alone is going to be half

【在 g*****g 的大作中提到】

: It's not going to be as fast as pure client side framework,
: and it never will.
: But you are still only updating a portion of the page at
: a time. So called AJAX. The generation of that portion is
: done on server side, I think it's going to be faster than
: request-based frameworks where the entire page is sent over
: the wire.
: The other drawback would be memory consumption in the session.
: Overall it's still very Swing and certainly fits a lot of
: projects.