On Wed, 2008-01-16 at 23:28 +1100, nash wrote: > > > Most annoying part of the protocol to be frank ;-) Hence if there were > > > mandatory filters, I'd do something like: > > > connect mesg > > > -> reply > > > getFeatures (protocol requires I believe) > > > > Nope, only the connect message is required. > > Saved a message then ;-)
Actually I think you should be able to send these frames as the first ones, - get features - get games We could easily add the server identification string to both of those frames (and it actually makes sense too). Lee, why did we ever want a connect frame anyway? It's pretty easy to tell if you have a valid TP frame quickly. <snip> > > You could do this, but you have to be careful about when you enable the > > filters. The server too will have to be careful (of which tpserver-cpp > > isn't > > yet) to make sure that synchronised. > > Not that hard... anything sent _after_ the filters message will assume > it's on, all replies after will too. Just a check of sequence number... This doesn't work for filters like SSL encryption. You can't do any encryption until the SSL negotiation has finished. <snip> Tim 'Mithro' Ansell _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
