| 03:59:26 | captain_proton | hey tim |
| 05:20:14 | captain_proton | hey tim |
| 05:31:58 | captain_proton | wb tim |
| 05:45:02 | XEpsilon | hi |
| 05:45:06 | captain_proton | hi |
| 06:27:51 | captain_pistachio | hey dog |
| 06:37:05 | finalfantasydog | 3l |
| 06:37:09 | finalfantasydog | heylas |
| 06:49:18 | captain_pistachio | BZFlag, are you there? |
| 07:26:04 | BZFlag | sometimes |
| 16:35:22 | captain_proton | hey tim |
| 16:41:36 | captain_proton | tim - read my xml thingy |
| 16:41:39 | captain_proton | is away: I'm probably eating |
| 16:46:25 | BZFlag | http://bzflag.org/wiki/view.php?topic=BZFlagXML&web=Main is empty. where is it? |
| 18:48:20 | captain_pistachio | its linked off the main wiki page - i got fed up with their form screwing up |
| 19:21:36 | captain_pistachio | tim - my thing is linked off the main wiki page |
| 19:41:56 | BZFlag | I copied it into the wiki... |
| 19:42:09 | captain_pistachio | ok |
| 19:42:13 | captain_pistachio | what did you think? |
| 19:46:12 | BZFlag | interesting. Explain: Here a benefit of XML comes into play. One could theoretically add a name attribute to the teleporters, and change the link definiton to something like |
| 19:46:12 | BZFlag | this: |
| 19:46:12 | BZFlag | <link from="tele1" fromside="0" to="tele2" toside="1"> |
| 19:46:30 | BZFlag | looks like tele1 and tele2 are just numbers anyway. no? |
| 19:46:41 | BZFlag | heh |
| 19:48:50 | BZFlag | also just moving to XML will NOT solve the flag imcompatibility issue. |
| 19:49:32 | BZFlag | client and servers will need to negotiate which flags are/will be in use (as opposed to which they can handle) |
| 19:49:50 | BZFlag | this is a sequence of new messages. They could be added to either protocol. |
| 19:50:20 | BZFlag | ditto for registered players. |
| 19:51:26 | BZFlag | your paragraph on incompatibilities actually covers that quite well. |
| 19:52:17 | BZFlag | in short: I don't see that XML offers any advantage over the current scheme other that readability. readability is perhaps by itself a compelling reson though. |
| 19:54:50 | BZFlag | any versioning negotiation that will or won't be added is orthogonal to the XML issue. |
| 19:56:42 | captain_pistachio | yeah |
| 19:56:44 | captain_pistachio | oh well |
| 19:56:47 | captain_pistachio | i'm going to work |
| 19:57:03 | BZFlag | I'm not saying it's a bad idea. |
| 19:57:06 | captain_pistachio | is away: at work |
| 19:57:34 | BZFlag | if it can be done with minimal overhead, readability is a big win for debugging. |
| 19:59:48 | BZFlag | If I'm going to revamp the net code (and I'd like to!) My top priority goals are: 1 - better play on slow connections especially in large games. 2 - much larger possible games, I'd like to see servers with max connections set in the hundreds. |
| 20:00:23 | BZFlag | 3 - better firewall support |
| 20:00:39 | BZFlag | 4 - UDP only connections |
| 20:01:47 | Disconnect | ibot: disconnect++ |
| 20:01:49 | Disconnect | hah |
| 20:02:05 | BZFlag | 5 - possible, but not required nick registration |
| 20:02:51 | BZFlag | 6 - complete handling of "unknown player" issues. so clients and servers can be forced to resync and have the same world view. |