Thank you Gaurav.
I am very silly. I was working around an artificial restriction. I did not
want images being uploaded to my website beyond 85kb. I used
<httpRuntime maxRequestLength="85"/>
to enforce this. That meant i couldn't upload datasets bigger than 85kb. Now
that i actually think about it and the power of the dotNet framework, i can
just add another web.config to my webservices directory that overrides this
setting
<httpRuntime maxRequestLength="500"/>
And now I get to have my cake and eat it too.
Thanks
"Gaurav Vaish (
www.EduJiniOnline.com)"
[quoted text, click to view] <gaurav.vaish.nospam@nospam.gmail.com> wrote in message
news:OtyipQM5GHA.3420@TK2MSFTNGP02.phx.gbl...
>> instance a 47kb data using my method can blow out to 120kb??? What is the
>> reccomnded way of calculating the size of the data to be transferred so
>> that
>
> I don't think it would be possible before hand because of various reasons:
>
> 1. Namespace prefixes to be used would be unknown
> 2. Indentation needs to be taken care of
> 3. Encoding needs to be taken care of... though normally it's UTF-8.
> 4. You may not know what 'exact' data would be Xml-Serialized and their
> namespaces (and may be new prefixes)...
>
>
> --
> Happy Hacking,
> Gaurav Vaish |
http://www.mastergaurav.com >
http://www.edujinionline.com >
http://articles.edujinionline.com/webservices > -------------------
>
>