[00:08:12] PK has quit: Connection timed out
[01:05:48] iceeey has joined #peragro-dev
[01:05:48] ChanServ sets mode: +o iceeey
[07:08:32] sueastside has joined #peragro-dev
[07:08:32] ChanServ sets mode: +o sueastside
[10:26:56] caedes has joined #peragro-dev
[10:26:57] ChanServ sets mode: +v caedes
[14:54:57] thebolt changed nick to: thebolt|away
[16:02:14] caedes has quit: "nightmare reset by peer"
[16:51:15] caedes has joined #peragro-dev
[16:51:15] ChanServ sets mode: +v caedes
[17:20:33] <iceeey> thebolt, got time to talk? :)
[17:20:47] <thebolt> sure
[17:21:02] <thebolt> school-day is over (its 17:20 ;)
[17:21:18] * iceeey starts on wed.
[17:21:35] <thebolt> ah :) i started last wednesday;)
[17:21:44] <iceeey> here are some ideas i drew up: http://rafb.net/p/Q1TpQJ10.html
[17:22:33] <thebolt> let my brain start up.. just came in from the -10 outside;)
[17:22:45] <iceeey> heh
[17:25:22] <thebolt> hm..
[17:28:45] <iceeey> the main idea is that server entities have all the database mapping in place, and client ones don't.. and they both share network serialization code
[17:34:08] <thebolt> as for the reinvent the wheel on DB section, i think some of this stuff (such as the db interaction, the networking component etc) is better writte in c++
[17:34:38] <iceeey> i figured you'd say that :)
[17:34:44] <iceeey> it's probably true
[17:35:27] <iceeey> but i still want a pretty looking python api
[17:35:46] <thebolt> well, i mean the python code shouldn't have to deal with that stuff at all
[17:36:41] <thebolt> then for network i think it is desirable not only to have automatic syncronization of all properties, but also for some objects that you can specify your own syncronization packet layout and scheduling
[17:36:50] <iceeey> yes absolutely
[17:37:01] <thebolt> so you say "this set of properties go into one packet, synced at most ever N ms at priority class B" etc
[17:37:33] <iceeey> trouble is how to specify all of that without getting too complex, and without sacrificing speed
[18:57:55] thebolt changed nick to: theboltMakingStu
[19:46:27] PK has joined #peragro-dev
[19:46:27] ChanServ sets mode: +o PK
[19:48:48] theboltMakingStu changed nick to: thebolt
[20:07:49] sueastside has quit: Read error: 104 (Connection reset by peer)
[20:07:54] |sueasts| has joined #peragro-dev
[20:09:51] |sueasts| changed nick to: sueastside
[20:10:15] ChanServ sets mode: +o sueastside
[22:20:22] sueastside has quit: "There's that thing people do when they do things."
[22:32:54] iceeey has quit: Read error: 110 (Connection timed out)
[22:33:54] iceeey has joined #peragro-dev
[22:33:54] ChanServ sets mode: +o iceeey
[22:48:50] iceeey has quit: "Leaving"
[23:28:13] caedes has quit: Read error: 104 (Connection reset by peer)
[23:28:40] caedes has joined #peragro-dev
[23:28:40] ChanServ sets mode: +v caedes
[23:31:27] caedes has quit: Client Quit