Ticket #237 (closed Enhancement: fixed)
Full composite structure in update requests
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1 |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.9 |
Keywords: | Cc: | ||
Complexity: | 5 | Area: | Application Framework / API |
Module: |
Description
The full composite structure must be contained in update requests. In particular the child topic IDs must be known in order to process multiple-value topics. This is needed for #76 "Many Cardinality".
Note: in #146 this format change has already be done for server->client communication. Now this ticket catches up with client->server communication.
Change History
comment:2 Changed 13 years ago by Jörg Richter
Webclient: introduce class PageModel? (#237).
That is TopicRenderer?.PageModel?
In preparation of "Full composite structure in update requests".
See ticket 237
comment:3 Changed 13 years ago by Jörg Richter
Webclient: new update request format (#237).
Update requests contain the full composite structure.
Change field renderer contract: read_form_value() returns an entire topic model, not just a simple value.
Server-side processing is pending.
See ticket 237
comment:4 Changed 13 years ago by Jörg Richter
Core: process new update request format (#237).
There are 2 topic serialization formats supported now:
1) canonic format -- contains entire topic models.
2) compact format -- contains the topic value only (simple or composite).
This format remains there to keep the simple cases simple.
Webbrowser plugin needs to be adadpted.
Furthermore in Webservice module: improve exception handling.
See ticket 237
comment:5 Changed 13 years ago by Jörg Richter
- Status changed from accepted to closed
- Resolution set to fixed
comment:6 Changed 13 years ago by Jörg Richter
Webclient: introduce class PageModel? (#237).
That is TopicRenderer?.PageModel?
In preparation of "Full composite structure in update requests".
See ticket 237
comment:7 Changed 13 years ago by Jörg Richter
Webclient: new update request format (#237).
Update requests contain the full composite structure.
Change field renderer contract: read_form_value() returns an entire topic model, not just a simple value.
Server-side processing is pending.
See ticket 237
comment:8 Changed 13 years ago by Jörg Richter
Core: process new update request format (#237).
There are 2 topic serialization formats supported now:
1) canonic format -- contains entire topic models.
2) compact format -- contains the topic value only (simple or composite).
This format remains there to keep the simple cases simple.
Webbrowser plugin needs to be adadpted.
Furthermore in Webservice module: improve exception handling.
See ticket 237
comment:9 Changed 13 years ago by Jörg Richter
comment:10 Changed 13 years ago by Jörg Richter
Webclient: fix editing simple topics.
Partly revert commit 0dc588 (April 10):
Change field renderer contract again: read_form_value() returns a simple value or a topic reference (REF_PREFIX notation), not an entire topic model.
Partly revert commit e13a55 (April 13):
Adapt to field renderer contract.
Furthermore: fix rendering of non-viewable/non-editable pages.
See ticket 237
comment:11 Changed 13 years ago by Jörg Richter
Webclient: fix editing simple topics.
Partly revert commit 0dc588 (April 10):
Change field renderer contract again: read_form_value() returns a simple value or a topic reference (REF_PREFIX notation), not an entire topic model.
Partly revert commit e13a55 (April 13):
Adapt to field renderer contract.
Furthermore: fix rendering of non-viewable/non-editable pages.
See ticket 237
comment:12 Changed 13 years ago by Jörg Richter
Webclient: introduce class PageModel? (#237).
That is TopicRenderer?.PageModel?
In preparation of "Full composite structure in update requests".
See ticket 237
comment:13 Changed 13 years ago by Jörg Richter
Webclient: new update request format (#237).
Update requests contain the full composite structure.
Change field renderer contract: read_form_value() returns an entire topic model, not just a simple value.
Server-side processing is pending.
See ticket 237
comment:14 Changed 13 years ago by Jörg Richter
Core: process new update request format (#237).
There are 2 topic serialization formats supported now:
1) canonic format -- contains entire topic models.
2) compact format -- contains the topic value only (simple or composite).
This format remains there to keep the simple cases simple.
Webbrowser plugin needs to be adadpted.
Furthermore in Webservice module: improve exception handling.
See ticket 237
comment:15 Changed 13 years ago by Jörg Richter
comment:16 Changed 13 years ago by Jörg Richter
Webclient: fix editing simple topics.
Partly revert commit 0dc588 (April 10):
Change field renderer contract again: read_form_value() returns a simple value or a topic reference (REF_PREFIX notation), not an entire topic model.
Partly revert commit e13a55 (April 13):
Adapt to field renderer contract.
Furthermore: fix rendering of non-viewable/non-editable pages.
See ticket 237