- Global Chapter::getLocalizedData ($key, $preferredLocale=null)
- Chapters should have access to their publication's locale and should fall back to that after the user's current locale and before the last fall back to the first data available.
- Global PhpXmlRpc\Client::$method
- : do these need to be public?
- Global PhpXmlRpc\Client::setCookie ($name, $value='', $path='', $domain='', $port=null)
- check correctness of urlencoding cookie value (copied from php way of doing it...)
- Global PhpXmlRpc\Helper\Charset::$charset_supersets
- add to iso table the characters from cp_1252 range, i.e. 128 to 159? These will NOT be present in true ISO-8859-1, but will save the unwary windows user from sending junk (though no luck when receiving them...)
- Global PhpXmlRpc\Helper\Charset::encodeEntities ($data, $srcEncoding='', $destEncoding='')
do a bit of basic benchmarking (strtr vs. str_replace)
make usage of iconv() or recode_string() or mb_string() where available
- Global PhpXmlRpc\Helper\XMLParser::guessEncoding ($httpHeader='', $xmlChunk='', $encodingPrefs=null)
- explore usage of mb_http_input(): does it detect http headers + post data? if so, use it instead of hand-detection!!!
- Global PhpXmlRpc\Request::$payload
- : do these need to be public?
- Global PhpXmlRpc\Request::parseResponseFile ($fp)
- add 2nd & 3rd param to be passed to ParseResponse() ???
- Global PhpXmlRpc\Response::$val
- : do these need to be public?
- Global PhpXmlRpc\Response::__construct ($val, $fCode=0, $fString='', $valType='')
- add check that $val / $fCode / $fString is of correct type??? NB: as of now we do not do it, since it might be either an xmlrpc value or a plain php val, or a complete xml chunk, depending on usage of Client::send() inside which creator is called...
- Global PhpXmlRpc\Value::$me
- : do these need to be public?
- Global PhpXmlRpc\Value::addArray ($values)
- add some checking for $values to be an array of xmlrpc values?
- Global PhpXmlRpc\Value::addStruct ($values)
- add some checking for $values to be an array?
- Class PhpXmlRpc\Wrapper
use some better templating system for code generation?
implement method wrapping with preservation of php objs in calls
when wrapping methods without obj rebuilding, use return_type = 'phpvals' (faster)
- Global PhpXmlRpc\Wrapper::buildMethodSignatures ($funcDesc)
- support better docs with multiple types separated by pipes by creating multiple signatures (this is questionable, as it might produce a big matrix of possible signatures with many such occurrences)
- Global PhpXmlRpc\Wrapper::buildWrapFunctionClosure ($callable, $extraOptions, $plainFuncName, $funcDesc)
validate params? In theory all validation is left to the dispatch map...
add support for $catchWarnings
- Global PhpXmlRpc\Wrapper::buildWrapFunctionSource ($callable, $newFuncName, $extraOptions, $plainFuncName, $funcDesc)
- add a nice phpdoc block in the generated source
- Global PhpXmlRpc\Wrapper::buildWrapMethodClosure ($client, $methodName, array $extraOptions, $mSig)
- should we allow usage of parameter simple_client_copy to mean 'do not clone' in this case?
- Global PhpXmlRpc\Wrapper::wrapPhpFunction ($callable, $newFuncName='', $extraOptions=array())
decide how to deal with params passed by ref in function definition: bomb out or allow?
finish using phpdoc info to build method sig if all params are named but out of order
add a check for params of 'resource' type
add some trigger_errors / error_log when returning false?
what to do when the PHP function returns NULL? We are currently returning an empty string value...
add an option to suppress php warnings in invocation of user function, similar to server debug level 3?
add a verbatim_object_copy parameter to allow avoiding usage the same obj instance?
add an option to allow generated function to skip validation of number of parameters, as that is done by the server anyway
- Global PhpXmlRpc\Wrapper::wrapXmlrpcMethod ($client, $methodName, $extraOptions=array())
allow caller to give us the method signature instead of querying for it, or just say 'skip it'
if we can not retrieve method signature, create a php function with varargs
allow the created function to throw exceptions on method calls failures
if caller did not specify a specific sig, shall we support all of them? It might be hard (hence slow) to match based on type and number of arguments...
- Global PKP\Services\PKPSubmissionService::getPropertyReviewAssignments ($submission)
- account for extra review stage in omp
- Global PKP\Services\PKPSubmissionService::getPropertyReviewRounds ($submission)
- account for extra review stage in omp
1.8.17