[
https://issues.redhat.com/browse/WFLY-13077?page=com.atlassian.jira.plugi...
]
Paul Ferraro moved EAP7-1436 to WFLY-13077:
-------------------------------------------
Project: WildFly (was: JBoss EAP Planning for version 7 and
above)
Key: WFLY-13077 (was: EAP7-1436)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow
2.0)
EAP PT Pre-Checked (PC): (was: TODO)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
Support protostream-based marshalling of user objects
-----------------------------------------------------
Key: WFLY-13077
URL:
https://issues.redhat.com/browse/WFLY-13077
Project: WildFly
Issue Type: Feature Request
Reporter: Paul Ferraro
Priority: Major
Currently, WildFly uses JBoss Marshalling to marshal user objects (session attributes,
SFSB instances) for the purposes of replication and persistence.
Protostream (developed by the Infinispan team) offers several advantages over JBoss
Marshalling.
* Lower memory footprint (marshalling schemas are built during compilation time)
* Faster marshalling - as it does not rely on reflection
* Produces generally smaller replication payloads (see
https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG...
)
* Resolves security concerns due to JBM's reliance on reflection and Java
serialization inherently permitting arbitrary execution of rogue code
* JBoss Marshalling is effectively in maintenance mode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)