ixman:Hi, Check the binding... It must be WSHttpBinding... and is slow... Do you need security or encryption?If not, disable them. If you don't have a problem with opening a TCP port in your firewall use NetTcpBinding, is almost as fast as remoting. Regards,
Alas, Silverlight only supports Basic HTTP binding.
Wait, are you saying you are trying to use the data portal to transfer 10MB of raw data?
Don't do that!! Really!!
The Silverlight data portal is designed to move business objects between Silverlight and .NET. To make this possible we had to do a lot of work around serializing and encoding object data, and I don't think that can be avoided when dealing with object graphs. In other words the overhead is required and unavoidable.
But you must realize that serialization incurs overhead that is not necessary for raw data, and it seems silly to incur that overhead when you don't need to.
Just set up another WCF service on your web/app server, define your own data contract for your raw data, and transfer the data directly through WCF, not through the data portal.
I
do not believe this product will work well with CSLA for Silverlight because the
message is already in binary format by the time it gets to WCF, so this product
will not give you much. You can use Fiddler to confirm this. You
can also find an example of Silverlight compression for CSLA under samples in
SVN. It is using CSharpZipLib.
Sergey Barskiy
Principal Consultant
office: 678.405.0687 |
mobile: 404.388.1899
Microsoft Worldwide Partner of the Year | Custom
Development Solutions, Technical Innovation
From: Paul Czywczynski
[mailto:cslanet@lhotka.net]
Sent: Friday, June 12, 2009 12:28 PM
To: Sergey Barskiy
Subject: Re: [CSLA .NET] Is WcfProxy 30 times slower then RemotingProxy?
We are using a custom formatter and compression.
http://www.noemax.com/products/fastinfoset/index.html
If anyone has anymore ideas to tweak more speed out of WCF I am all ears.
-Paul
Copyright (c) Marimer LLC