Re: JFreeciv experiences

That's pretty much how it's been working so far.
It *is* a bit of an arduous manual task when we move up to a new stable version of freeciv: having done the network protocol upgrade from 1.8 => 1.10 and then again from 1.10 => 1.12, I can testify that it was only slightly more fun than peeling potatoes ;) It'd be really cool if we could find a way to automate this, as the code is fairly monotonous (I thought a bit about generating code from XML descriptions of the protocol, but never got further than just thinking...)
Brian





On Fri, 22 Mar 2002, Ben Mazur wrote:
> The C version of freeciv has made an effort not to break the protocol
> format in quite a while.

The C version exists in two versions - a stable release 1.12.0, and a
development version that is continually under development and which will
eventually become the new stable release.

As far as I know, jfreeciv communicates with stable freeciv servers, not
development servers. So the network protocol should be same until 1.13 is
released.

The C version tries to be backwards and forwards compatible in the network
protocol using capabilities, which jfreeciv should probably know about one
day. For now it is probably simpler to just communicate with stable server
releases.

jfreeciv looks very promising.

Yours,
Per
(c developer)

"Capitalism is the extraordinary belief that the nastiest of men,
for the nastiest of reasons, will somehow work for the benefit of
us all." -- John Maynard Keynes