Another interesting direction would be to use Matt Morrow's vaccum infrastructure to make a neat, almost completely general, serialization mechanism.
It's not safe, and can traverse any value that doesn't contain functions or unevaluated thunks, but would be very helpful for sending values like `cycle [1,2,3]` over the network. He and I were talking about writing such a library before he disappeared, but it doesn't seem terribly difficult if you have a good use for it. Dan On Fri, Aug 6, 2010 at 11:14 AM, Frank Kupke <f...@informatik.uni-kiel.de>wrote: > Paul, > Yes, I use Read and Show to serialize. I thought of switching to Binary > myself but could not find the time yet ;-) Now, a student here is going to > work on that. Also, as TCP communication involves a lot of overhead, the > library makes some efforts to reduce the amount of messages and makes > message exchange itself quite efficient which resulted in a significant > efficiency gain. But, there is definitely more optimization potential > buried... > > Frank > Am 06.08.2010 um 00:49 schrieb Paul Johnson: > > Looks interesting. One point: you seem to be using Read and Show > typeclasses for serialisation. I think you would be better off using > Binary, which is much more efficient. > > Paul. > > On 03/08/10 09:35, Frank Kupke wrote: > > Hi, > > DSTM is an implementation of a robust distributed Software Transactional > Memory (STM) library for Haskell. Many real-life applications are distributed > by nature. Concurrent applications may profit from robustness added by > re-implementation as distributed applications. DSTM extends the STM > abstraction to distributed systems and presents an implementation efficient > enough to be used in soft real-time applications. Further, the implemented > library is robust in itself, offering the application developer a high > abstraction level to realize robustness, hence, significantly simplifying > this, in general, complex task. > > The DSTM package consists of the DSTM library, a name server application, > and three sample distributed programs using the library. Provided are a > simple Dining Philosophers, a Chat, and a soft real-time Bomberman game > application. Distributed communication is transparent to the application > programmer. The application designer uses a very simple name server mechanism > to set up the system. The DSTM library includes the management of unavailable > process nodes and provides the application with abstract error information > thus facilitating the implementation of robust distributed application > programs. > > For usage please look into the documentation file: DSTMManual.pdf. > > The package including the documentation can be found > on:http://hackage.haskell.org/package/DSTM-0.1.1 > > > Best regards, > Frank Kupke > > > > _______________________________________________ > Haskell-Cafe mailing > listhaskell-c...@haskell.orghttp://www.haskell.org/mailman/listinfo/haskell-cafe > > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > > > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
