Based on a quick glance through the deRPC classes in the packages you listed, it does indeed appear to be deRPC. Note that deRPC has always been marked as experimental, and is now deprecated, and that either RPC or RequestFactory should be used instead.
Details that seem to confirm this:
com.google.gwt.rpc.client.impl.SimplePayloadSink#RPC_SEPARATOR_CHAR
is a constant equal to the~
character, which appears to be a separator between different tokens in the sample string you provided.Both
com.google.gwt.rpc.client.impl.SimplePayloadSink and
com.google.gwt.rpc.server.SimplePayloadDecoder` have many comments that appear to depict the same basic format that you are seeing in there:// "4~abcd
inendVisit(StringValueCommand x, Context ctx)
closely matches several tokens in the sample string - a quote indicating a string, an int describing the length, a~
separator, then the string itself (this doesnt match everything, I suspect because you removed details about the service and the name of the method):"3~F7e
"3~B0e
"1~b
Booleans all follow
Z1
orZ0
, as in your sample string