Closed GoogleCodeExporter closed 9 years ago
It is briefly explained at the bottom of
http://code.google.com/p/pathway-commons/wiki/cPathSquaredWebService#Test_Links
Unlike cPath (where IDs were simple and short), in cPath2 we do our best to
keep original provider's IDs unchanged (except for some utility class elements,
where we have to normalize in order to merge pathway data from different
sources).
URI (actually everything that is used as url parameter) must be properly
encoded. Some browser are "smart" enough to replace spaces with %20 at least,
but not all that has to be. This is normal. However, there is no such problem
when the webservice used via a standard client API, which usually does
encoding/decoding transparently for you.
Original comment by rod...@gmail.com
on 26 May 2011 at 8:47
Original comment by rod...@gmail.com
on 5 Jan 2013 at 12:06
Original issue reported on code.google.com by
cer...@gmail.com
on 26 May 2011 at 7:53