I don't believe you can create arbitrarily long messages like those shown in your link because your client and server must agree on the number and order of fields before transfer.
[Time, Longitude, Latitude, Height, Time, Longitude, Latitude, Height, ...]
Problem: without pre-defining many field numbers, how do I pass this many fields?
Option 1
Instead, you can create your own message type to represent a single instance:
message CartographicRadians {
string time = 1;
double longitude = 2;
double latitude = 3;
double height = 4;
}
Then use the custom type as a field. Here the repeated
keyword indicates that you can send more than one CartographicRadians
in the CartographicRadiansArray
.
message CartographicRadiansArray {
repeated CartographicRadians entries = 1;
}
Option 2
Another approach would be to create a self-recursive message which would function closer to the stream-like format described above.
message CartographicRadians {
string time = 1;
double longitude = 2;
double latitude = 3;
double height = 4;
CartographicRadians nextEntry = 5;
}
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…