public interface DevConsoleRPCTab
DSRequests sent from your application. Tracking is activated by checking the "Track RPCs" box at the top of the tab.
The main "RPC History" list shows the transactions that have been sent from your application
since the session began (since you checked the "Track RPCs" box or refreshed your browser,
whichever happened most recently). Each entry in the list represents either a server
roundtrip, a DSRequest to a clientOnly DataSource or a direct request to a webservice.
Request queues are shown as separate
entries, with the requests
that made up the queue shown indented beneath it.
Each entry in the RPC History list shows useful diagnostic information, including:
Smart GWT and Smart GWT Server can gather detailed profiling information for a
request/response roundtrip, and display it in the Developer Console. Note, the server-side
information is only available for DSRequests, and only if you are using the Smart GWT
Server module. Extra levels of server-side detail are available if you are also using one
of Smart GWT Server's built-in DataSource types (note, at the time of writing this only
applies to SQLDataSource). Note, detailed timing information is derived using the
RPCManager.getTimingData() API: you
can programatically derive exactly the same
timing metrics by calling that method from your own code
DSRequest.returnTimingData: truein your
server.propertiesfile. This will cause server timing information to be gathered and returned for every DSRequest from every client
RPCManager.enabledBuiltinMethodssetting of your
server.propertiesfile (these builtin RPCs should already be enabled in a development environment). When these built-in RPCs are enabled, server timing data can be switched on and off on a per-client basis, via a checkbox in the Developer Console.
isc.RPCManager.setTimingEnabled(true)before invoking your DSRequest. Pass false to the same API to switch timing off again.
DSRequest.allowReturnTimingData: falsein your
server.propertiesfile. This will unconditionally prevent server timing information from being gathered; it beats the methods mentioned above for gathering server timings
The timing data is tree-structured; a node with an opener next to it can be expanded to drill into more detail:
The following important points apply to the detailed timing information: