[gwt-contrib] How to generate chart with live data in GWT RPC?

[Arif]

Hello,
I have a Java simulation program that I'd like to run as a GWT RPC
application.
The output of the simulation is a time-series graph. Now, I need to
develop a dynamic chart: as the simulation progresses in time, and
more data is available from my server, I need to display the updated
chart (on the client's browser).

Could you please advise with any tutorial/complete example on how to
do this using HighCharts (or any other charting module) in a GWT RPC
app?
I have (very) basic knowledge with GWT RPC.
Any help would be appreciated.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Avoid Java bottleneck by using explicit Charset for byte[]<->String conversions (issue1588803)

[t . broyer]

LGTM, but I'm not a Googler sorry. You'll have to find a reviewer and
committer.


http://gwt-code-reviews.appspot.com/1588803/diff/2001/src/com/google/gwt/user/server/rpc/RPCServletUtils.java
File src/com/google/gwt/user/server/rpc/RPCServletUtils.java (right):

http://gwt-code-reviews.appspot.com/1588803/diff/2001/src/com/google/gwt/user/server/rpc/RPCServletUtils.java#newcode379
src/com/google/gwt/user/server/rpc/RPCServletUtils.java:379:
response.getOutputStream().write(GENERIC_FAILURE_MSG.getBytes(getCharset("UTF-8")));
CHARSET_UTF8 instead?

http://gwt-code-reviews.appspot.com/1588803/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Avoid Java bottleneck by using explicit Charset for byte[]<->String conversions (issue1588803)

[t . broyer]

Given that only UTF-8 is used, how about an eagerly-initialized
RPCServletUtil.UTF8_CHARSET instead? (similar to Guava's Charsets.UTF_8
[1])

[1]
http://docs.guava-libraries.googlecode.com/git-history/v10.0.1/javadoc/com/google/common/base/Charsets.html#UTF_8

http://gwt-code-reviews.appspot.com/1588803/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Fix com.google.gwt.http.client.UrlBuilder to encode the query string using URL.encodeQueryString(). (issue1586804)

[jlabanca]

LGTM

http://gwt-code-reviews.appspot.com/1586804/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Fix com.google.gwt.http.client.UrlBuilder to encode the query string using URL.encodeQueryString(). (issue1586804)

[t . broyer]

I'm a bit late but:

Note that it fixes
http://code.google.com/p/google-web-toolkit/issues/detail?id=4940



http://gwt-code-reviews.appspot.com/1586804/diff/1/user/src/com/google/gwt/http/client/UrlBuilder.java
File user/src/com/google/gwt/http/client/UrlBuilder.java (right):

http://gwt-code-reviews.appspot.com/1586804/diff/1/user/src/com/google/gwt/http/client/UrlBuilder.java#newcode53
user/src/com/google/gwt/http/client/UrlBuilder.java:53:
url.append(URL.encode(protocol)).append("://");
Maybe should rather be URL.encodeComponent(protocol, false), or, as it's
deprecated, URL.encodePathComponent(protocol).

http://gwt-code-reviews.appspot.com/1586804/diff/1/user/src/com/google/gwt/http/client/UrlBuilder.java#newcode76
user/src/com/google/gwt/http/client/UrlBuilder.java:76:
.append(URL.encodeQueryString(entry.getKey()))
encodePathSegment is faster, as is won't change %20 to + (which is done
in a second pass).
As an alternative, if we really want +s for spaces in the query-string,
appending to another StringBuilder using encodePathSegment, and then
replacing /%20/g with + before appending to the 'url' StringBuilder
would be faster than encodeQueryString as done here.
But maybe this is premature optimization?

http://gwt-code-reviews.appspot.com/1586804/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors