In short, that??™s exactly what DWR provides.
DWR was, if not the first, then certainly the first to rise to prominence that provides this
approach of treating server-side code like JavaScript running in the browser. Subsequently,
other libraries have been created (or some existing ones expanded) to do things much like
DWR does, but DWR holds the distinction of doing it first (first in the sense of being well
known for it) and many would say still to this day does it best.
So, why should you choose DWR over other options? The answer, of course, as hopefully
you??™ve already realized on your own, is maybe you shouldn??™t. Did I just hear a gasp? Seriously,
any developer worth his most likely too small paycheck will always explore his options and
recommend the solution that fits the current problem best (ignoring the all-too-common
???corporate standards??? paradigm where you don??™t have the freedom to do that). By all means,
you should investigate the other options first, write some little pilot apps with each, and see
which one fits your requirements the best. DWR will almost certainly rise to the top couple of
choices, and in a great many cases it??™ll fit the bill perfectly.
Pages:
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123