Proto commits in gwtproject/gwt

These 15 commits are when the Protocol Buffers files have changed:

2011-07-13

tag the 2.4-rc1 release git-svn-id: https://google-web-toolkit.googlecode.com/svn/tags/2.4.0-rc1@10448 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2011-02-10

tag for the release of GWT 2.2 git-svn-id: https://google-web-toolkit.googlecode.com/svn/tags/2.2.0@9722 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2010-10-07

Add tag for gwt 2.1.0 rc1 git-svn-id: https://google-web-toolkit.googlecode.com/svn/tags/2.1.0-rc1@8974 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2010-04-26

Merged trunk r7931 into this branch. Fixes a couple of issues with the RemoteUI and GPE DevMode view interaction. svn merge -c7931 --ignore-ancestry https://google-web-toolkit.googlecode.com/svn/trunk git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@7975 8db76d5a-ed1c-0410-87a9-c151d255dfc7

The documentation is generated from this commit.

2010-04-16

Fixes a couple of issues with the RemoteUI and GPE DevMode view interaction. The problem is GPE shows the startup URLs in the DevMode view _before_ the modules were fully loaded. The root issue is GPE does not receive the moduleLoadComplete message. When we went to push this message to GPE, we discovered the protobuf is too restricted: the RequestType cannot have new values and maintain backwards compatibility. This is because requestType is a "required" field, so older GPE versions will not understand the new moduleLoadComplete message and thus have an undefined requestType, at which point an error is thrown because requestType is required. For the protobuf issue, this patch changes the "required" to "optional". We will still have compatibility issues with GWT or GPE versions earlier than this patch, but this allows for future versions to have new values added to the enums. It is up to the application layer to check the validity of the message. For the GPE startup URL issue, it will show a "Loading" state as soon as DevMode is launched. Then, GWT will send the startup URLs in moduleLoadComplete. Upon receiving these, GPE will display them. The user will not see startup URLs before they are ready. Review at http://gwt-code-reviews.appspot.com/323801 Review by: rdayal@google.com git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@7931 8db76d5a-ed1c-0410-87a9-c151d255dfc7

The documentation is generated from this commit.

2009-11-24

Merging trunk@r7150 into releases/2.0. git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@7151 8db76d5a-ed1c-0410-87a9-c151d255dfc7

Got rid of port-guessing logic. We now use setStartupURLs as our init hook. We no longer send over the dev mode query params. We send over the startup URLs. Review by: mmendez git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@7150 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2009-11-09

Merges trunk@6762 into releases/2.0. Merge performed with the following command: svn merge --ignore-ancestry -c 6762 https://google-web-toolkit.googlecode.com/svn/trunk . git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@6763 8db76d5a-ed1c-0410-87a9-c151d255dfc7

Changes to the Message wire format: -requestId has become message id, and message id has been moved up as a field of Message, as opposed to Request -a new type of Message, called Failure, has been added. The Failure message is used to indicate that a request failed on the server side. Now that this message type has been added, we can now report faliures back over the wire, and throw exceptions on the client side NOTE: Server request failures result in RuntimeExceptions in ViewerServiceClient, which means that the DevMode server will shut down. Review by: mmendez git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@6762 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2009-11-06

Merged trunk@6730 was merged into this branch Adds the needsAttention flag to the remote UI protocol. svn merge --ignore-ancestry -c 6730 https://google-web-toolkit.googlecode.com/svn/trunk . git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@6731 8db76d5a-ed1c-0410-87a9-c151d255dfc7

Adds the needsAttention flag to the remote UI protocol. Review by: rdayal git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@6730 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2009-10-30

Merged r6559 into branch. svn merge --ignore-ancestry -c 6559 http://google-web-toolkit.googlecode.com/svn/trunk/ . http://code.google.com/p/google-web-toolkit/source/detail?r=6559 git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@6561 8db76d5a-ed1c-0410-87a9-c151d255dfc7

Modified the remote UI protocol to send an initialization message with the client id. The client id is passed in as an argument on the command line. The purpose of this "dance" is to give us a way to associate a running launch configuration with an incoming remote UI connection on the plugin side. We also need to pass the browser channel port and the web server port as part of the initialization message (in order to construct the launch URLs). To be able to do this at ui.initialize, we had to change the auto-port selection logic to substitute in a free port number (which we compute) instead of 0. That way, we know what ports the browser channel and the web server will be on before they start up. Patch by: rdayal, mmendez (pair prog) git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@6559 8db76d5a-ed1c-0410-87a9-c151d255dfc7

2009-10-21

Cherrypick trunk@6432 was merged into this branch, Merge branch 'remote-ui-communication' at r6431 into trunk. svn merge --ignore_ancestry -c 6432 https://google-web-toolkit.googlecode.com/svn/trunk . git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/2.0@6433 8db76d5a-ed1c-0410-87a9-c151d255dfc7

Merge branch 'remote-ui-communication' at r6431 into trunk Review by: rdayal Conflicts: branch-info.txt git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@6432 8db76d5a-ed1c-0410-87a9-c151d255dfc7