Well digging into it more, I've since realized the whole approach I was taking is misguided anyway, as serialization appears to be for marshaling the data of already defined classes. What I was really trying to do was create new classes (java or clojure), and stream them across the network, and have them executed on other side by a system that only knew the 'parent' class or interface. But I believe this will require custom class loading from bytes on the other side.
I still suspect though there will be issues when trying to mix dynamic clojure-created classes with serialization, due to its data types not being serializable. Some of the customizations for java serialization might offer a way out, but uncertain.. Also, I don't have clojure on both sides; unfamiliar with thrift/ protocol buffers, will look them up. Thx --n > If you've got Clojure available on both ends, you can serialize with > (pr-str...) and deserialize with (read...). Only works with pure- > Clojure data structures, tho. > > Maybe you could use Clojure to generate a native Java collection like > ArrayList and serialize that. > > Another option is something like Thrift or Protocol Buffers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
