Maybe it would be easy to implement geobuf as third (and fast) option format for geting features. For instance, you must use tile vectors or image for feature source with more than 7000 linestrings. Tile vectors are of limited usage, destroying features topology and projections are reduced to web Mercator. If we overcome long geojson download, mapguide-rest with all its possibilities would be the best webGIS server by far...
Geobuf is a protobuf-based format. This means it's a non-starter if I can't find library that can write protobuf messages. This library also has to be pure PHP as well as relying on native protobuf libraries means mapguide-rest loses its easy portability.
Geobuf, like every other mapbox-based protobuf spec they is based on proto2 messages, which last I checked has weak to non-existent PHP tooling/codegen support. If it was a proto3-based spec, then at least I know I can tap into a wealth of codegen tools because they're all proto3 based.
Maybe it would be easy to implement geobuf as third (and fast) option format for geting features. For instance, you must use tile vectors or image for feature source with more than 7000 linestrings. Tile vectors are of limited usage, destroying features topology and projections are reduced to web Mercator. If we overcome long geojson download, mapguide-rest with all its possibilities would be the best webGIS server by far...