Re: Serialized object compression

Re: Serialized object compression

Old forum URL:

ozitraveller posted on Tuesday, August 10, 2010

Hi all

My problem is: I have a very large object graph that I need to transport and I'm using clsa 1.5  with .Net 1.1 (sorry I can't change to a later version this is production code).

I'm looking for some input on how I can overcome this problem. It's an urgent matter so if anyone has any ideas please post them.

Ok, so far, I've been through the forum and there is quite a bit of information for later technology but not the stoneage stuff.

thanks in anticipation




RockfordLhotka replied on Wednesday, August 11, 2010

CSLA 1.x only uses Remoting. Remoting has been out of favor for several years.

However, years ago there was a small Russian company that had a Remoting channel that did compression. If they still exist, or if their product is out there somewhere, it might help you.

Otherwise you'll need to rework the data portal code to meet your needs. You can borrow some ideas from CSLA 2.0 or later I'm sure.

ozitraveller replied on Wednesday, August 11, 2010

Thanks Rocky. Appreciate your quick response.

I'll have to have a look at reworking the data portal as there is not much chance of moving to a later Clsa version anytime soon.

RockfordLhotka replied on Wednesday, August 11, 2010

Conceptually the easiest thing to do is what I did with the asmx implementation in 2.0 - where the service interface works on byte arrays. That allows (requires) you to run the BinaryFormatter yourself on client and server, and thereby allows you to just run the resulting byte stream through the compression engine of your choice.

You should be able to use much of the existing data portal proxy and host code as a model - just change the host public methods to accept and produce byte arrays, and change the client-side proxy code to do the same.

Copyright (c) Marimer LLC