Ask a Question related to ASP.NET Web Services, Design and Development.
-
Kevin Burton #1
Ineroperability of Webservice arguments.
I have a web service that takes and returns a byte []. As
long as I have a .NET client this seems to work OK. I was
wondering if I would be better off from an interop
standpoint to change the argument and return to a base64
encoded string?
Any ideas?
Kevin
Kevin Burton Guest
-
required arguments in Flex 1.5 - kills webservice
I am running Flex1.5 with Tomcat 5.0. I dropped the samples.war file in webapps and everything worked great. I am planning to use on example, the... -
JVM Arguments
hello, I would like to know if we can define several directories for the "libPath" attribute in the coldfusion MX 7 administrator to have different... -
Getting URL arguments
I'm trying to read the arguments of the URL for the document. I'm new to PHP and can't figure it out. I've played around with $_SERVER but the... -
using 'do' with arguments
hello im wondering if you can pass arguments with the 'do' command? like: on event h = "handler" -
Little problem with arguments
Hi, I just insalled php4.3.2 on my windows xp windows... everything works ok, but when i try to do: test.php ----------- <?php... -
Saurabh Nandu #2 Re: Ineroperability of Webservice arguments.
Hi Kevin,
internally the bytes get converted to Base64 in .NET during transmission.
For interoperablity purposes its better to use Base64 encoding. I have
worked with web serives returning images, and i use the same base64 strings
as parameters.
Reagrds,
Saurabh Nandu
Saurabh Nandu Guest
Reply With QuoteSimilar Questions and Discussions
Posting Permissions
- You may not post new threads
- You may post replies
- You may not post attachments
- You may not edit your posts
