Index Changes
Page Difference

Difference between version and version     

Back to Fuji DJBI Design Arch, or Fuji DJBI Design Arch Info


At line 11 changed 1 line.
----
At line 67 added 10 lines.
----
!! Serialization/Deserialization
The MessageExchange goes through a serialization and deserialization phase as part of the sending and receiving process. The previous section discussed the messages and their contents.\\
\\
Some interesting issues/decisions come up in this process:
* Properties of MessageExchange's and NormalizedMEssage's have as a value an arbitrary Java object. Obviously, if the object doesn't support serialization than it can't be sent. This currently results in a exception and the ME being terminated with an ERROR condition. It has been suggested that there be a configuration setting that allows these to just be ignored.
* Normalized message content is typed as a Source. Typically it would be a DOMSource. The serialization process convert this to StreamSource for placement on the wire, and also uses it as the actual type on the received MessageExchange. The receiver has to be prepared for any kind of Source, but a conversion to DOMSource is likely. May want to investigate if the Proxy Binding can get from DOMSource->???->DOMSource is a faster manner than Source transformations.
* NormalizedMessage attachments are type as a DataHandler. These are streamed out using DataHandler supported methods and on the receiving side a special StreamDataSource is used a the container.
\\
The serialization process is by far the most expensive part of the Proxy Binding. The normal ME interactions are basically just routing decisions. It's likely that the serialization process could take advantage of the a worker thread pool to get better scalability.
At line 68 removed 2 lines.
Serialization/Deserialization
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-10) was last changed on 24-Sep-08 15:15 PM, -0700 by DerekFrankforth