CCON problems

[shrinktofit]

• CCON can not be merged like existing JSON merge mech.

• CCON splits a resource into two parts on some platforms.

• CCON requires a not well-known extension .cconb or .ccon and it's forbidden on many platforms.

[shrinktofit]

The extension name problem is relatively easy to solve. The proposed solution is:

• Refactor BufferAsset so that it can be serialized as CCON format. After this change, .bin extension will no longer be occupied by BufferAsset. PR: [Target 390]Serialize BufferAsset as CCON #15513

• Output CCON files with extension ".bin". Whenever asset system downloading a file with .bin extension, that file is recognized and parsed as CCON files:

  • Engine: No longer output .ccon(b) extension #15993
  • Editor: https://github.com/cocos/cocos-editor/pull/2425
  • Engine Extension: https://github.com/cocos/engine-extensions/pull/337
  • Platform Extension: https://github.com/cocos/creator-runtime-extensions/pull/467