Receive post data not known at design time
(Created page with "With MDriven Turnkey it is easy to construct public Rest services of strict model typed data as defined by a ViewModel as described here. Sometimes you may however have the n...") |
No edit summary |
||
| Line 1: | Line 1: | ||
With MDriven Turnkey it is easy to construct public Rest services of strict model typed data as defined by a ViewModel as described here. | With MDriven Turnkey it is easy to construct public Rest services of strict model typed data as defined by a ViewModel as [[Rest Services In MDriven|described here]]. | ||
Sometimes you may however have the need to receive data in a post that is not known at design time. | Sometimes you may, however, have the need to receive data in a post that is not known at design time. | ||
One specific scenario we have seen was the integration of the Texture-online-editor, this editor will post all the document data as several form files - but we do not know the names of these files or their number - at design time. | |||
To handle his case we have introduced the following pattern: | |||
Revision as of 11:08, 20 July 2019
This page was created by Hans.karlsen on 2019-07-20. Last edited by Edgar on 2025-01-20.
With MDriven Turnkey it is easy to construct public Rest services of strict model typed data as defined by a ViewModel as described here.
Sometimes you may, however, have the need to receive data in a post that is not known at design time.
One specific scenario we have seen was the integration of the Texture-online-editor, this editor will post all the document data as several form files - but we do not know the names of these files or their number - at design time.
To handle his case we have introduced the following pattern: