gmane.comp.games.tp.devel

Re: Testing

Ivan Ruchkin — 2011-03-23T07:49:55

Received all three messages. It works.
*

Best regards,
Ivan Ruchkin*


2011/3/23 Landon Fowles <tp< at >lfowles.org>

Re: Test again

Zhang Chiyuan — 2011-03-23T06:14:26

"again again again" from tp-devel< at >thousandparsec.net: icmp_req=1 ttl=52
time=224 ms
"again again again" from tp-devel< at >thousandparsec.net: icmp_req=2 ttl=52
time=216 ms
"again again again" from tp-devel< at >thousandparsec.net: icmp_req=3 ttl=52
time=228 ms
"again again again" from tp-devel< at >thousandparsec.net: icmp_req=4 ttl=52
time=229 ms
"again again again" from tp-devel< at >thousandparsec.net: icmp_req=5 ttl=52
time=231 ms
^C
--- tp-devel< at >thousandparsec.net test statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 216.887/224.345/231.074/4.086 ms

2011/3/23 Nash <nash< at >nash.id.au>

Re: Testing

Landon Fowles — 2011-03-23T06:05:20

And I received both of these messages!

On Tue, Mar 22, 2011 at 04:26:43PM +1100, Tim Ansell wrote:



--
Landon Fowles
http://lfowles.org

Test again

Nash — 2011-03-23T06:07:55

again again again.

Re: Testing

Tim Ansell — 2011-03-22T05:26:43

I received this message!

Tim

On Tue, Mar 15, 2011 at 12:50 PM, Lee Begg <llnz< at >paradise.net.nz> wrote:

Testing

Lee Begg — 2011-03-15T01:50:36

Sorry, just testing the mailing lists.

Regards
Lee

Mailing lists currently unstable

Tim Ansell — 2010-12-06T02:00:40

Hey guys,

Someone is currently trying to use the Thousand Parsec mailman instance to
perform backscatter spam. I'm currently trying to disable it but it is
causing issues.

Tim

Re: Changes to Makefiles to add SQLite Persistence

Lee Begg — 2010-07-08T21:42:22

Greg: I'm glad you got in touch on IRC, my email had been down for the 
last few days.

Thanks Ruchkin for replying.

Later
Lee

Ivan Ruchkin wrote:

Re: Changes to Makefiles to add SQLite Persistence

Ivan Ruchkin — 2010-07-06T19:33:15

Re: Changes to Makefiles to add SQLite Persistence

Gregory Lew — 2010-07-06T18:46:08

________________________________________
From: tp-devel-bounces< at >thousandparsec.net [tp-devel-bounces< at >thousandparsec.net] On Behalf Of Gregory Lew [gregory.lew< at >mail.mcgill.ca]
Sent: Tuesday, July 06, 2010 2:44 PM
To: tp-devel< at >thousandparsec.net
Subject: [tp-devel] Changes to Makefiles to add SQLite Persistence

Hi Everyone,

I've been working on a sqlite persistence module for GSOC and I was wondering if someone could help me.
I know I need to add things to the makefiles for it to be compiled with the tpserver-cpp, but I'm not sure exactly what needs to be added or changed.

Thanks,
Greg
_______________________________________________
tp-devel mailing list
tp-devel< at >thousandparsec.net
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel

Changes to Makefiles to add SQLite Persistence

Gregory Lew — 2010-07-06T18:44:28

Hi Everyone,

I've been working on a sqlite persistence module for GSOC and I was wondering if someone could help me.
I know I need to add things to the makefiles for it to be compiled with the tpserver-cpp, but I'm not sure exactly what needs to be added or changed.

Thanks,
Greg

Re: "Object isn't new enough" error (issue 97)

Lee Begg — 2010-06-17T21:18:34

Issue located.

It appears the objectivew doesn't get the underlying object 
modtime/serial when the object is completely visible (which is what it 
used to do). I will fix this later today.

Later
Lee

Re: "Object isn't new enough" error (issue 97)

Lee Begg — 2010-06-17T20:54:51

Ok. I will check out that code soon. That bit was extensively changed in 
last years GSoC.

Thanks, that helps isolate it.


Because an order queue (and hence an object) can be updated (add/remove) 
many times within a turn by a player who has permission to the orderqueue.

Later
Lee

_______________________________________________
tp-devel mailing list
tp-devel< at >thousandparsec.net
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel

Re: "Object isn't new enough" error (issue 97)

Null — 2010-06-17T09:31:31

Re: "Object isn't new enough" error (issue 97)

Lee Begg — 2010-06-16T21:38:40

I've just checked the code, it all seems fine.

Is the problem between the serial number (new name for modtime) in the ID List 
and the actual object?


Could it be that it means that it's not in the ID List, because the list only 
asked for items newer than a date?


That's because it isn't really the same object, everyone's view of the object 
is different.




Let's get a bit more detail, but I happy to help.

Regards
Lee

"Object isn't new enough" error (issue 97)

Damjan Košir — 2010-06-16T11:26:45

Error with python cache use

Joey — 2010-06-14T08:10:55

Re: Parsek and KDE dependency

Marwan Hilmi — 2010-05-28T16:19:55

Parsek and KDE dependency

marcel.hauf — 2010-05-28T16:03:03

Hello thousand parsec developers,

I was thinking about Parseks KDE dependency and how much it binds the users to 
KDE and its huge base libs. While looking for a way to implement KWallet 
support. I wondered why Parsek has KDE as a dependency. If I take a look at 
how much KDE code is used in Parsek, it isn't much and I am wondering if it is 
necessary to keep Parsek as an KDE app or move away from that dependency.
That are just some thoughts.

I told llnz about my thoughts on IRC and he suggest to discuss this on the 
mailing list and also get some input from JLP.
He had also some points.
First, "being in KDE means that if we can get parsek into kdegames, a lot more 
people will have a client, and might play".
Second, "if we can get away with less or no direct KDE dependencies than that 
might also work"

About the second point, it is possible to get some native KDE features without 
KDE as dependency, mainly through DBus, since KDE 4 exposes a lot of features 
like KNotify and KWallet. Moving to pure Qt m

Re: Protocol specification error

Lee Begg — 2010-05-21T10:30:11

Good catch. I've now fixed it.

Later
Lee

On Fri, 21 May 2010 05:33:35 Damjan Košir wrote:

Protocol specification error

Damjan Košir — 2010-05-20T17:33:35

While looking at protocol specifications for design packet and client 
code I've found something interesting.

In tp.netlib.objects.Design design ID and last modified time are 
specified as SInt types, but in the protocol specifications they are 
specified as UInt.

Also in the protocol specification it says "If adding a design send the 
ID as -1". You can not send a UInt with a value of -1.

The protocol specifications should be updated to fit the implementation 
(and perhaps save someone from a headache in the future ^_^)

Damjan 'Null' Košir