a:8:{s:9:"#provides";s:16:"dojox.rpc.Client";s:9:"#resource";s:13:"rpc/Client.js";s:16:"dojo._defaultXhr";a:2:{s:7:"private";b:1;s:7:"summary";s:0:"";}s:8:"dojo.xhr";a:5:{s:4:"type";s:8:"Function";s:10:"parameters";a:2:{s:6:"method";a:1:{s:4:"type";s:0:"";}s:4:"args";a:1:{s:4:"type";s:0:"";}}s:6:"source";s:841:"		var headers = args.headers = args.headers || {};
		// set the client id, this can be used by servers to maintain state information with the
		// a specific client. Many servers rely on sessions for this, but sessions are shared
		// between tabs/windows, so this is not appropriate for application state, it
		// really only useful for storing user authentication
		headers["Client-Id"] = dojox.rpc.Client.clientId;
		// set the sequence id. HTTP is non-deterministic, message can arrive at the server
		// out of order. In complex Ajax applications, it may be more to ensure that messages
		// can be properly sequenced deterministically. This applies a sequency id to each
		// XHR request so that the server can order them.
		headers["Seq-Id"] = dojox._reqSeqId = (dojox._reqSeqId||0)+1;
		return dojo._defaultXhr.apply(dojo,arguments);";s:6:"chains";a:1:{s:4:"call";a:1:{i:0;s:16:"dojo._defaultXhr";}}s:7:"summary";s:0:"";}s:25:"dojox.rpc.Client.clientId";a:1:{s:7:"summary";s:0:"";}s:16:"dojox.rpc.Client";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}s:9:"dojox.rpc";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}s:5:"dojox";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}}