N***m
发帖数: 4460 | 1 ZK框架，感觉server端啥都得做，效率是不是很低？
这样的话是不是只有小型站点才适合？ | s******e
发帖数: 493 | 2 not really.
ZK is an ajax framework. The chance is that if you choose an ajax, you
rarely can stay on the client side to get the info you need. | N***m
发帖数: 4460 | 3 3x for your input.
I just start to touch ZK, but the book said even for
a click button event that hasn't really done anything,
the event will be sent to server side because ZK
takes control of almost everything for clients. That eases
the updating of browser, but that also seems to me a
serious drawback. I guess that is what a framework is, you
manipulate things inside quite well but lose some
flexibility in certain cases?
【在 s******e 的大作中提到】
: not really.
: ZK is an ajax framework. The chance is that if you choose an ajax, you
: rarely can stay on the client side to get the info you need.
| g*****g
发帖数: 34805 | 4 You worry too much. Scalability is not an issue until
it's an issue. And for average website, it may never
be an issue.
ZK is one of so called stateful component frameworks, components
are rendered on server side. But traditional request-based
frameworks are done this way too. The main advantage of ajax,
is updating only a portion of webpage so that the update can
be fast. Reducing IO isn't as important. That being said, as
long as it's ajax framework, you can still expect less traffic
than request-based framework. Request-based frameworks are still
widely used in most of all your financial websites. Stateful
frameworks use more memory footprint than request-based ones,
that's what people worry about in terms of scalability. But 64bits
JVM is an option now and memory is cheaper than ever.
I mean, unless you are developing google or facebook and you may have
a concern and a pure client side ajax framework is necessary. Otherwise
you can worry about it when you have 100K users.
【在 N***m 的大作中提到】
: 3x for your input.
: I just start to touch ZK, but the book said even for
: a click button event that hasn't really done anything,
: the event will be sent to server side because ZK
: takes control of almost everything for clients. That eases
: the updating of browser, but that also seems to me a
: serious drawback. I guess that is what a framework is, you
: manipulate things inside quite well but lose some
: flexibility in certain cases?
| N***m
发帖数: 4460 | 5 谢谢你的回复。还没开始正式学ZK，如你所说的，如果
不是问题的话，以后应该会有机会用到的。
【在 g*****g 的大作中提到】
: You worry too much. Scalability is not an issue until
: it's an issue. And for average website, it may never
: be an issue.
: ZK is one of so called stateful component frameworks, components
: are rendered on server side. But traditional request-based
: frameworks are done this way too. The main advantage of ajax,
: is updating only a portion of webpage so that the update can
: be fast. Reducing IO isn't as important. That being said, as
: long as it's ajax framework, you can still expect less traffic
: than request-based framework. Request-based frameworks are still
|
|
