MemoryFileProvider stores only in memory. Invalid names, duplicate IDs/names, invalid parents and cyclic moves are rejected. File operations are asynchronous. The capabilities set determines visible actions. txFileStore supports loading and optional removal; renaming is not offered as a store update.
HTTP uploads require your own multipart POST endpoint. fieldName defaults to file. With chunkSize, the server must assemble the protocol agreed through chunkFields. Retrying starts from the beginning. The HTTP adapter reads the file into memory and reports progress after completed chunks. File pickers/drop and save dialogs depend on OS and plugins; onDownload enables custom saving.
Map tiles use {z}/{x}/{y}. Configure tile sources, credentials and attribution yourself. The application calls GeoAdapter and binds its results as markers/routes. Without a source, no implicit external map request is made.