I noticed the ZipFile is not serializable.
\r\nWe would like to expose the zipfile via webservice to a client, just wondering if you happen to any suggestions/workaround to achieve this.
\r\nThanks
\r\nNP
", "PostedDate": "2009-09-18T02:18:51.23-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "236181", "ThreadId": "69353", "Html": "What do you mean by "expose the zipfile"?
\r\nwhat exactly is involved in exposing a zipfile to a client via a web service?
", "PostedDate": "2009-09-18T12:03:59.11-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "236348", "ThreadId": "69353", "Html": "Sorry about the confusion. I meant to say sending the zip file via a web service.
\r\nIf i try to serialize the zip file i get an exception indicating it is not serializable.
\r\nThanks
\r\nNP
", "PostedDate": "2009-09-18T22:58:40.117-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "236349", "ThreadId": "69353", "Html": "If the zipfile is in memory, why don't you send it as a stream?
\r\nIf the zipfile is on the filesystem, you can just read the file and send it as you would any file.
\r\nI don't understand why you want to send a ZIpFile object.
\r\nCan you explain your scenario again please? what is it that you really want to do? Are you trying only to send a compressed data stream across the wire?
\r\nif that's the case why a zipfile? Why not just use a DeflateStream or ZlibStream or GZipStream ?
\r\n", "PostedDate": "2009-09-18T23:11:44.777-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "236735", "ThreadId": "69353", "Html": "
Cheeso wrote:\r\n
\r\nIf the zipfile is in memory, why don't you send it as a stream?
\r\nIf the zipfile is on the filesystem, you can just read the file and send it as you would any file.
\r\nI don't understand why you want to send a ZIpFile object.
\r\nCan you explain your scenario again please? what is it that you really want to do? Are you trying only to send a compressed data stream across the wire?
\r\nif that's the case why a zipfile? Why not just use a DeflateStream or ZlibStream or GZipStream ?
\r\n\r\n
Thanks Cheeso for that.
\r\n>>Are you trying only to send a compressed data stream across the wire?
\r\nYes, this is exactly what i am trying to do as the zip file may contain a large number of files.
\r\nTo be able to send in a web service the objects need to be serializable.
\r\nI will look into the streams as you said and see if it would help.
\r\nThanks
\r\nNP
\r\n", "PostedDate": "2009-09-20T20:30:16.033-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "236986", "ThreadId": "69353", "Html": "
pathurun wrote:\r\n
\r\nCheeso wrote:\r\n
\r\nIf the zipfile is in memory, why don't you send it as a stream?
\r\nIf the zipfile is on the filesystem, you can just read the file and send it as you would any file.
\r\nI don't understand why you want to send a ZIpFile object.
\r\nCan you explain your scenario again please? what is it that you really want to do? Are you trying only to send a compressed data stream across the wire?
\r\nif that's the case why a zipfile? Why not just use a DeflateStream or ZlibStream or GZipStream ?
\r\n\r\n
Thanks Cheeso for that.
\r\n>>Are you trying only to send a compressed data stream across the wire?
\r\nYes, this is exactly what i am trying to do as the zip file may contain a large number of files.
\r\nTo be able to send in a web service the objects need to be serializable.
\r\nI will look into the streams as you said and see if it would help.
\r\nThanks
\r\nNP
\r\n\r\n
funny this is almost what i am doing from the sound of it.
\r\nhere are some snips of code:
\r\non hh that gets a zip:\r\n string Base64Text = string.Empty; <font size="1">\r\n Base64Text = Srv.GetUpdateInfo( ); // web method call <font size="1">\r\n On Server to send data: \r\n [WebMethod] return datastring; thats one way to do this for a file on disk to download to a hh device.
byte[] Raw = { 0, 0, 0, 0 };
Raw = Convert.FromBase64String(Base64Text);
FileStream Fs = File.Create("\\\\FlashDisk\\\\Up\\\\Update.Zip", Raw.Length / 8);
Fs.Write(Raw, 0, Raw.Length);
Fs.Flush();
Fs.Close();
data is now on hh flash disk as a zip file.
public string GetUpdate() {
string datastring = string.Empty;
datastring = Convert.ToBase64String(
System.IO.File.ReadAllBytes(
this.Server.MapPath(
"~/App_Data/Update." + WebConfigurationManager.AppSettings["CurrentVersion"] + ".zip")
),Base64FormattingOptions.InsertLineBreaks);\r\n
}
If you are transmitting a large file, you might want to look into streaming the file content.
\r\n", "PostedDate": "2009-09-21T12:53:25.98-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "237018", "ThreadId": "69353", "Html": "
I haven't done this, but if I were building it, I would first try this:
\r\ndefine a service contract that allowed the client to provide a stream to the server. The stream on the client might be a filestream or a memory stream. The server would then produce the zip file and then save it to the stream provided by the client. The client can then do what it wants with the zip content.
\r\nIf that does not work, for whatever reason, a simple file transfer approach would also work. Here again I'd use streaming though, to avoid the requirement that all zip content be kept in memory.
\r\nif you're not concerned about keeping all the content in memory at one time , then use the approach given above, by figuerres, where the content is sent all as one large base64 string. Encoding it that way will inflate the data on the wire significantly, so I'd recommend that only for small zip files, and when performance is not a concern.
\r\n\r\n
", "PostedDate": "2009-09-21T13:00:45.28-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "237203", "ThreadId": "69353", "Html": "
Thanks very much for your input Cheeso and Figurres. I will give it a try and see how it works.
\r\nThanks
\r\nNP
", "PostedDate": "2009-09-22T01:30:19.203-07:00", "UserRole": null, "MarkedAsAnswerDate": null }, { "Id": "238506", "ThreadId": "69353", "Html": "Cheeso wrote:\r\n
\r\nI haven't done this, but if I were building it, I would first try this:
\r\ndefine a service contract that allowed the client to provide a stream to the server. The stream on the client might be a filestream or a memory stream. The server would then produce the zip file and then save it to the stream provided by the client. The client can then do what it wants with the zip content.
\r\nIf that does not work, for whatever reason, a simple file transfer approach would also work. Here again I'd use streaming though, to avoid the requirement that all zip content be kept in memory.
\r\nif you're not concerned about keeping all the content in memory at one time , then use the approach given above, by figuerres, where the content is sent all as one large base64 string. Encoding it that way will inflate the data on the wire significantly, so I'd recommend that only for small zip files, and when performance is not a concern.
\r\n\r\n
\r\n
i am fairly sure that for an asmx or wcf over http that http will send the data in chunks as http packets, i guess the issues would be the use of .ReadAllBytes .... one could read a chunk and send it with a seq number... then the reciving side could get 1, get 2, get 3 and so on....
\r\nthe .net cf limits a lot of what we can do with wcf and stuff..... I *WISH* they had put in support for WCF over sockets with Binary serialization! I have about 80 devices that all upload data every day.... https soap is kinda big chunks.
\r\n", "PostedDate": "2009-09-24T13:51:08.75-07:00", "UserRole": null, "MarkedAsAnswerDate": null } ]