FWD » Core Development » Runtime Infrastructure

When the FWD OpenClient calls are made from the same JVM as the FWD server, there are lots of immutable objects being serialized and deserialized. This includes the table schema (options, fields, etc) and even rows (here we can use just the immutable Java types associated with the BDT type).

An example is PropertyDefinition which is immutable but is serialized in the same JVM.

The impact will be most likely on a high-load server.

Also, if I'm not mistaken, the REST/SOAP/etc APIs will benefit from this, also.

It seems that the most cases were immutable objects are being serialized and deserialized are coming from AppServerHelper.preProcessParameters and AppServerHelper.postProcessResult. Here if the local flag (flag indicates that appserver is running in the same JVM as the requester) is set, there is some code that executes serialization and deseralization of such structures as TableWrapper, DatasetWrapper.

Serialization of this fields triggers serialization of its child immutable fields (PropertyDefinition, IndexDefinition, IndexComponentDefinition, etc).

I wrote some methods to handle the copy of the structures, and get rid of serialization from preProcessParameters and postProcessResult.

Committed on 11488a, rev. 16597.

Constantin Asofiei wrote:

Eduard, the changes are good. Please go with testing the #10529 app, #10614 app, ETF and any other app which uses appservers.

Ok, should I post the update example projects?

#10529 app, #10614 app, ETF have been tested.

GUI application smoke tests + SOAP tests, GUI application unit tests and CHUI regression tests passed.

Anything else remaining?

Constantin Asofiei wrote:

Anything else remaining?

Waiting on response for Gui application smoke tests.

Eduard Soltan wrote:

Waiting on response for Gui application smoke tests.

Smoke tests on large GUI application passed.