Closed lucataglia closed 6 years ago
@lucaRadicalbit I'll do that this weekend. It's actually an omission. I plan to make ProtoSerializable
extend Serializable
. :)
@lucaRadicalbit In what context are you using tensors that requires them to extend Serializable
?
@eaplatanios Because we are using a distributed system that need to send the tensors along the cluster and the tensors need to be serializable. I don't know why during the last few days the problem I had regarding the lack of the Serializable interface is gone. So if it's a problem for you API you can avoid to put that interface on your class for the moment. If I have the same problem in the future I'll write to you
@lucaRadicalbit It's not a problem per se, but I was wondering what serialization framework you're using. I thought that Protobuf serialization support should be ok and you can explicitly provide the serializer and deserializer methods to the framework. I'm not sure what's the best way to implement the Serializable
interface. It could be done using Protobuf, but for your use case, it might be better to just pass along the memory representation of the tensor directly. How are you handling serialization currently?
@lucaRadicalbit Let me know if you have any updates on this, otherwise I'll go ahead and close it for now.
This is the signature of the Tensor class. Unfortunately for my application I need that Tensor extend also Serializable. Any chance that you can add that interface to you class ?