Hello, thank's for the quick answer !
I tried with IE, FF and Chrome. The result is the same.
I profiled the client with the Chrome plugin Speed Tracer : I thought there was
no ambiguity. But I had a doubt because chrome is working strangely on my pc.
I then created a simple restlet client in order to test :
ClientResource resource = new
ClientResource("http://127.0.0.1:8888/restlet/operations/byAccDate/start01102010/end10102010";);
resource.get(MediaType.APPLICATION_JAVA_OBJECT_GWT).write(System.out);
There is no doubt : if i don't de-serialize, the performance is very good...
The pb is on the client side...
my first tests will be :
1/ desactivate every graphical update on the client side : done, no significant
result (13s)
2/ de-serialize the json string result in gwt
3/ try the Google Chrome Frame you mentionned
4/ ? any suggestion ?
Is there a way to improve the de-serialization with GWT ?
Should I modify my objects ?
Should I store the data corresponding to the "Operations" in tables / array
(not very familiar with javascript...)
Thank's !
Ben
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2699374
