Justin Clark-Casey (justincc) 1a988ba835 In remote QueryAccess, also receive the actual status (true|false) instead of always true no matter what the callee actually returned. ... This was due to two things 1) SimulationServiceConnector.QueryAccess was always looking to the outer result["success"]. But if a "_Result" map is returned (which is certainly the case right now), then the true success is _Result["success"], result["success"] is always true no matter what 2) If QueryAccess was false at the destination, then AgentHandlers.DoQueryAccess() was never putting this in the result. The default action of SerializeJsonString() is not to put false booleans in the JSON!!!, so this has to be explicitly set.		2012-05-31 02:17:55 +01:00
..
Base	Escape and unescape xml element names if necessary in ServerUtils.BuildXmlData() and ParseElement()	2012-05-10 00:50:20 +01:00
Handlers	In remote QueryAccess, also receive the actual status (true|false) instead of always true no matter what the callee actually returned.	2012-05-31 02:17:55 +01:00
ServerMain.cs	fission UserAccountService.HandleCreateUser() into two methods, one which handles user command parsing and another which actually does the work	2010-05-28 21:14:15 +01:00