• Is serialization of parameters and return values required?

Document Actions
Replies: 3   Views: 6803
Up one level
You need to be a registered member to post to this forum. Register now.
Prev topic | Next topic

 • Is serialization of parameters and return values required?

Posted by edwardotis at 2004-11-19 01:21
Is serialization of parameters and return values required?
Anonymous
Posts: n/a

 • Re: Is serialization of parameters and return values required?

Posted by havoyan at 2004-11-20 16:56
Neither seriliaziation or return type are required. Although it is required that parameters were either primitive type or of serializable types (most of Java JDK classes are serializable). It is not important for the current version but in the future parts can be distributed over the network and then the serialization of the messages will be used to send fired events to a remote part.
Manager
Posts: 0

 • Re: Is serialization of parameters and return values required?

Posted by edwardotis at 2004-11-22 06:27
So, when I pass an object from one part to another, I'm passing a pointer into an address space that both parts share?

I thought Buildap was not designed to behave in this manner.
Anonymous
Posts: n/a

 • Re: Is serialization of parameters and return values required?

Posted by havoyan at 2004-11-23 15:00
quite opposite. serialization is done via the framework - so that is why the parameters should be serilizable or primitive types. Parts should not share the same address space so passing as pointers is not an option. The question was: is serilization required - I guess from part side - and the answer is no - because serilization will be done within the framework. So if you ask me - should parameters be of serializable type - then the responce will be yes.
Manager
Posts: 0