Re: .NET Remoting, Windows Service host, load balancing

Hi,

See my inline comments.

Regards,


"Spam Catcher" <spamhoneypot@xxxxxxxxxx> wrote in message
news:Xns989580FF62CE4usenethoneypotrogers@xxxxxxxxxxxx
"yekerui" <nospam@xxxxxxxxx> wrote in
news:uaeMzNxGHHA.3268@xxxxxxxxxxxxxxxxxxxx:

Hi, Zoe Hart:

After reading though your message here, I would like to suggest
you to
use SocketPro at www.udaparts.com

After downloading SocketPro package and going through all of four
tutorials, specifically you should spend sometime to study tutorial
Four with detailed documentation and source code. SocketPro is written
from batch, asynchrony and parallel computation in mind. Believe me it
is SIGNIFICANTLY faster than .NET remoting under all of cases and
machines. That particular tutorial sample basically tells you how to
write a load balancing system, although it is not a 100% load
balancing system.

SocketPro looks neat, but too bad it doesn't it into Microsoft's Remoting
or WCF frameworks.

SocketPro not only looks neat, but also works great with special design. It
offers many and more key features than Microsoft's Remoting and WCF
frameworks can not provide. We can develop Remoting channels from SocketPro,
but it does not make sense for us to just fit SocketPro into Microsoft's
remoting. Doing so will degrade SocketPro.

Here is a big list of advantages of SocketPro over Microsoft's Remoting:

1. SocketPro is Significantly faster and more scalable than Microsoft's
Remoting under all of cases and machines.
2. SocketPro uses bi-directional TCP/IP 100% non-blocking socket, but
Microsoft's Remoting uses uni-directional TCP/IP synchronous socket for
communication.
3. SocketPro fully supports PocketPC, but Microsoft's Remoting does not.
4. SocketPro has no firewall and NAT problems, but Microsoft's Remoting
does have these problems.
5. SocketPro supports SSL/TLS very well, but Microsoft's Remoting does
not support SSL/TLS yet.
6. SocketPro has built-in supports for notifcation services among
clients, but Microsoft's Remoting does not.
7. SocketPro is a amazing framwork to solve a set of complex problems
like exchanging large files, large collections of .NET objects, and
mutli-threading, and is much better than Microsoft's Remoting in these
aspects.
8. SocketPro is extremely stable with all of types of networks, but
Microsoft's Remoting does not work good enough with dial-up network.
9. Client and server are not tightly coupled. For example, you can write
a 100% native coded server application to talk with 100% .NET client
application. You can't do something like this with Microsoft's Remoting.
10. SocketPro has built-in support with online zipping and un-zipping, but
Microsoft's Remoting does not.
11. SocketPro has much lower dependence, and requres much lower resources.
12. Many more .......


Does SocketPro handle .NET objects, or does it only marshal datatables?

SocketPro can remote any .NET objects using .NET serialization.




.

Relevant Pages
Loading