Lobby Protocol/Uberserver: Status?

[insaneinside]

The official TASProtocol documentation has been gone from the main Spring source tree since 0.77b4, and what was there before that wasn't up-to-date. As a lobby developer and lobby 'bot hobbyist, I have a definite interest in this, and anyone who wants to try his/her hand at protocol implementation is completely shut out.

Checked the only uberserver repository I could find (git://springlobby.info/git/aegis/uberserver.git) -- last updated in November. Is it still being developed? Is there another source tree I ought to be looking in? I'd rather not have to dig through someone else's code to figure out any protocol changes -- shouldn't have to, either, but I'm willing to resort to doing that for my own purposes if I need to.

I'd consider maintaining some sort of documentation for the protocol if I didn't have to dig through an implementation to find every new change.

[Satirik]

http://spring.clan-sy.com/websvn/listin ... rev=0&sc=0

[insaneinside]

Is that up-to-date? How long will it continue to be, if it is? When it is no longer up-to-date, will a new revision be checked in?

[koshi]

that protocol description was last edited 14 months ago by betalord...

as for protocol changes from tasserver to uberserver, we've been bugging aegis for that for as long as he said uberserver will be deployed soon

[AF]

tbh it was promised a long time ago and its important its released before and not with uberserver so we can adapt any bots we have. We can only really wait for aegis to comment on it though, he may just be snowed under with work.

[aegis]

yeah, I've been pretty busy.

according to tizbac, the current latest pushed uberserver is fairly stable excepting a mysql bug which may be fixed in my copy.

I'm going to make the protocol part of uberserver self-documenting today and upload a protocol description, and I'm also pushing the updated server sources while I write this.

edit:
pushed, will create the protocol description code later today.

[aegis]

its important its released before and not with uberserver so we can adapt any bots we have.

legacy protocol will be enabled by default, but deprecated.

the server will notify clients it supports the new protocol features, maybe by sending a command before TASSERVER.
updated clients will be able to respond to the new protocol, but legacy clients will still work flawlessly.

[AF]

I say that not because it would break our codebases, but because of the threat of obsoletion and competition from other implementations that went and implemented features ahead. Not ot mention time to ask adn refien our understanding of the semantic and quirks of the new protocol additions