Hi,
On Sunday 24 September 2006 18:19, Buchanan, Stuart wrote:
> > You will actually double the amount of memory that is transmitted for
> > one property.
>
> That is true. However, transmitting the chat strings is going to represent
> a much bigger increase in message size, though I've restricted the chat
> size to 128 characters per message. I should have highlighted this in my
> original patch just in case we're worried about bandwidth.
Yep, but the chat messages will happen every now and than. The properties will
be sent at each step. So this will hurt much more than the chat messages.
> > In the longer term, I would like to have a dynamic property
> > path/property type
> > negotiation that is done at the start of a connection.
>
> Me too, but re-writing the message format seemed quite sufficient for the
> moment :)
So, if we just store the type with that map, we do not even need to change the
message format.
- All old properties are floats.
- The old code ignores id's that it does not know about.
- The updated code will interpret old style floats correctly.
So, in this case there is no need to increase the protocol version.
Did I miss something?
> > Can you update your patch to avoid transmitting the type?
>
> Yes, but I can't provide any guarantee as to when I'll get it done.
Not a problem.
Greetings
Mathias
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
