SOAP
-
What are my options if I want to use SOAP for an application developed using eVC++ 4?
-
What are my options if I want to use SOAP for an application developed using eVC++ 4?
Try this: http://www.pocketsoap.com/[^] Regards, João Paulo Figueira Embedded MVP
-
Try this: http://www.pocketsoap.com/[^] Regards, João Paulo Figueira Embedded MVP
Thank you. One more question: Are there any issues in serializing a class in Pocket PC and desrializing it in Windows XP and vice-versa, or is this possible at all?
-
Thank you. One more question: Are there any issues in serializing a class in Pocket PC and desrializing it in Windows XP and vice-versa, or is this possible at all?
If you mean data binary compatibility with ARM, the answer is yes. You can serialize a structure to a file using
WriteFileon the desktop and read it on the Pocket PC withReadFile. Regards, João Paulo Figueira Embedded MVP -
If you mean data binary compatibility with ARM, the answer is yes. You can serialize a structure to a file using
WriteFileon the desktop and read it on the Pocket PC withReadFile. Regards, João Paulo Figueira Embedded MVPI'm only scratching the surface here. The application that I'm writing needs to transfer commands (text) and binary data (pictures) to and from Pocket PC. So, I'm trying to decide what is the best way to transfer the binary part. I'm not sure if using WriteFile would apply in my case, since I need to write to the disk first and read back again. A sort of in-memory solution would be more elegant, with no performance penalty. (I'm coming from C#, where you can serialize a class in memory and send it down the socket to be read by the other party) Any ideas? Your comments are valuable. ;)
-
I'm only scratching the surface here. The application that I'm writing needs to transfer commands (text) and binary data (pictures) to and from Pocket PC. So, I'm trying to decide what is the best way to transfer the binary part. I'm not sure if using WriteFile would apply in my case, since I need to write to the disk first and read back again. A sort of in-memory solution would be more elegant, with no performance penalty. (I'm coming from C#, where you can serialize a class in memory and send it down the socket to be read by the other party) Any ideas? Your comments are valuable. ;)
no_reg_name wrote: I'm not sure if using WriteFile would apply in my case, since I need to write to the disk first and read back again. What I meant is that data is read and written in the exact same way on the PPC and the Desktop. no_reg_name wrote: So, I'm trying to decide what is the best way to transfer the binary part. Don't change it: send it as it is. The Pocket PC will read it using the same code you use on the desktop. This will happen irrespective of the medium - I've already ported images on database blobs to and from the Pocket PC without any format changes. Regards, João Paulo Figueira Embedded MVP