thanks for the answer

ok, thank you

Thank you for the information. The optimal number of threads equals the number of processors on a system and it shouldn't exceed twice the processor count. Correct? Why not 3 times?

I have a quad core machine, how many threads can an application domain handle? How can I determine the capabilities of the machine at runtime to know how many buckets, and threads I can/should use?

Have you got any similar information that doesn't need knowledge of PHP?

I didn't mean that. The question was how to organize asynchronous upload of the file.

But 2 bits will be lost, won't they? (I am not strong in encodings...)

Ok, thank you, I'll think about this

How can I perform uploading files to the webserver without refreshing whole page? AJAX UpdatePanel and standard FileUpload do not work together...

I don't know, may be there is some special stream for sending file data from client to server at once, isn't there? -- modified at 5:09 Friday 31st August, 2007

But WCF is a part of .NET 3.0. Are there any methods to do this using .NET 2.0?

I understand that I can send only the data in the file. The question is how to represent this data for transfering through webservices? I want the memory size of my file data to be as small as it can be. For example, if I have an array of bytes, data that passes through webservices should look like this: (array)(byte)1(/byte)(byte)2(/byte)(/array). And it's not very good, because "byte" xml-nodes are repeated too often. And the string representation causes some problems with encodings.

Thank you for the answer, when I said "transform" I meant "load" but when passing through the webservices an array of bytes will be transformed to some xml-data, something like this: (array)(byte)1(/byte)(byte)2(/byte)(/array) This data contains a lot of unnecessary information (repeated "byte" nodes). Are there any techinques to send the file in more compact format that needs less memory size?

what is the best way to send an arbitrary file through webservices? (I think transforming it to an array of bytes is not a good idea...)