[svn] 4804: Bugs: LCDS-548: add code to deal with contentType="application/ xml" with one parameter (avoid

Question

Revision: 4804
Author: [email protected]
Date: 2009-02-02 17:56:22 -0800 (Mon, 02 Feb 2009)
Log Message:
Bugs: LCDS-548: add code to deal with contentType="application/xml" with one parameter (avoid
name/value encoding in that case)
LCDS-405: baseURL on HTTPMultiService should accept URLs which start with "/"
Added convertParametersHandler and convertResultsHandler function hooks to RemoteObject
to support framework code which wants to modify the service behavior.
Moved "properties" from rpc/http/AbstractOperation to rpc/AbstractOperation so we can use
it for customizing the handling of remote object results
Couple of minor ASDoc fixes and one tab -> spaces change
Doc: minor asdoc edits
QE: LCDS QE will verify the bugs in this one
Reviewers: Mete, Pete, Seth, Ed reviewed different parts of this checkin
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-548
http://bugs.adobe.com/jira/browse/LCDS-405
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractInvoker.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/HTTPMultiService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/RemoteObject.as

Answer 1

Hello,
How about this as an alternative:
Use a functional global which has 3 cases:
1. open config file - it opens the config file and reads the contents into a string (which is the functional global data), and you only do this one time at the beginning of the program.
2. edit config data - it edits the string, which are really the contents of the file, but doesn't worry about writing to the file.  you could even get fancy here, and allow an array of tags and an array of values as input, and it would go update/edit all the tags to have the corresponding values.
3.  close config file - it writes the current string data (the functional global data) to the file and closes it.
Using the functions in the string palette, I think you'll find most of the code for that module/functional global will be easy to write.
I hope this helps!
Best Regards,
JLS
Best,
JLS
Sixclear