One approach available today will be to decompose the data object you are publishing so that the embedded object is available as an independent item stream. That stream can then be split across multiple messages using the multi-part message paradigm. Where you previously wanted to place the container object now replace with a string with the new item name.

Rssl Container entries can be removed individually with appropriate "action" values, e.g. RSSL_MPEA_DELETE_ENTRY for a RsslMap. The entire container can be reset by sending out a REFRESH with the RSSL_RFMF_CLEAR_CACHE flag set.

I think that you can fragment map or vector field in the field list because both map and vector support actions. Map supports RSLSL_MPEA_ADD_ENTRY action while vector supports RSSL_VTEA_SET_ENTRY action.

Refer to UPA Developers Guide in section 11.3 Container Types, it mentions that "If the field entry contains another container type, action values associated with that type specify how to update the information."

For examples:

1. The first refresh message must contains all fields. Map's fields may contain some map entries with RSSL_MPEA_ADD_ENTRY action

2. The subsequent update messages contains updated fields. In update messages, you can add new map entries in the map's fields by using RSSL_MPEA_ADD_ENTRY action. To update or delete map entries in the map's fields, you can use RSSL_MPEA_UPDATE_ENTRY and RSSL_MPEA_DELETE_ENTRY respectively.

For more information regarding the usage and rules of map and vector actions, please refer to UPA Developers Guide.

Regarding field level clear cache, you should avoid sending the field twice in the same message because it can cause unexpected behaviour in consuming applications.