Leif Åstrand has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 11:
The existing test suite seems to have quite good coverage, but it
Leif Åstrand has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 11: Code-Review-1
This patch does not work as it stands for a couple of
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 11:
Sounds like we need more tests. Serialization code generally does
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#8).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 7:
(2 comments)
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#9).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#10).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 10:
Leeroy seems to be in a bad mood today :)
--
To view, visit
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#11).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 5:
(3 comments)
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#6).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#7).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 7:
(4 comments)
Looking good.
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#5).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 5:
Okay, so patch set 5 takes a much simpler approach and does not change
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 5:
(3 comments)
I like where this is going. As I understand it, all
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
Discussed this offline with Artur for some time last Friday and I like
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
On the server side, I don't think we need a max version? If the
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
Feasible? I'd guess yes. Up to the implementer to decide how they
Artur Signell has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
Would it be a feasible solution to introduce protocol version 8 today
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3:
(2 comments)
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#4).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
Patch Set 4 now bumps the default version number and changes the
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
(6 comments)
Looking at the history, I stumbled on another case
Matthew Dempsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
(1 comment)
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
(4 comments)
To add to the versioning mess, there are Google
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
(1 comment)
We need to take a decision re. supporting version 7 in
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 4:
Okay, I started a discussion in contrib:
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#3).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
Matthew Dempsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3:
(2 comments)
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3: -Code-Review
(1 comment)
That starts to look good.
As discussed
Matthew Dempsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3:
(2 comments)
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3:
The main reason I put up this patch is that currently IE9 is
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 3:
(3 comments)
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 2:
Brian:
The main reason I put up this patch is that currently IE9 is
John Ahlroos has uploaded a new change for review.
https://gwt-review.googlesource.com/2900
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Use JSON.parse() instead of eval() to
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1: Code-Review-2
(2 comments)
AFAICT, this change is kind of useless
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1:
Brian, I added you as a reviewer as you're the author of the RPC
Colin Alworth has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1:
(1 comment)
The ServerSerializationStreamWriter will also need
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1:
(2 comments)
Hello Leeroy Jenkins, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2900
to look at the new patch set (#2).
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
John Ahlroos has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 2:
Removed the protocol version for now since it will cause a lot of work
Thomas Broyer has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 2:
(1 comment)
As Colin said, this change is not backwards-compatible
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 2:
Haven't looked at the code yet, but it seems like we should rev the
44 matches
Mail list logo