headers
Jason McIntosh | 26 Jan 05:00
Picon

Re: Game history UI

On 1/25/06, Andrew Plotkin <erkyrath <at> eblong.com> wrote:
>
> We would need a way to refer to a particular game record. (That is, if you
> are browsing the game records, and you want to throw one at your client,
> there has to be a way to name it.) I suppose this would be the game URI
> plus a record number of some sort.

Why not skip the URI and just use a record ID string?

> What we want is an RPC "volity.game_history(data)". Actually, two RPCs.

Oh, yes, of course, this is what I think I meant to say...

Except that let's actually make this a bit more general (and useful)
by replacing it with these calls, which deal at the game record level
(which will include history, plus other useful metadata):

Client->Bookkeeper: volity.game_record($record_id)
Bookkeeper->Client: volity.game_record($record_id, $record)

The second argument in the latter call is a game record struct,
exactly as described in [[Game Record]]. I'm keeping the ID separate
just to avoid changing that specification by adding an ID field, but
maybe it should have one anyway...?

--
Jason McIntosh
zendonut <at> gmail.com
Jabber: jmac <at> volity.net
AIM: zendonut
(Continue reading)

Permalink | Reply |
headers
Andrew Plotkin | 26 Jan 05:34

Re: Game history UI

On Wed, 25 Jan 2006, Jason McIntosh wrote:

> On 1/25/06, Andrew Plotkin <erkyrath <at> eblong.com> wrote:
>>
>> We would need a way to refer to a particular game record. (That is, if you
>> are browsing the game records, and you want to throw one at your client,
>> there has to be a way to name it.) I suppose this would be the game URI
>> plus a record number of some sort.
>
> Why not skip the URI and just use a record ID string?

Works either way. If you have only a record ID string, then it has to be 
globally unique (at that bookkeeper), instead of being unique to that 
game. You're the bookkeeper implementor; you tell me which makes more 
sense. :)

>> What we want is an RPC "volity.game_history(data)". Actually, two RPCs.
>
> Oh, yes, of course, this is what I think I meant to say...
>
> Except that let's actually make this a bit more general (and useful)
> by replacing it with these calls, which deal at the game record level
> (which will include history, plus other useful metadata):
>
> Client->Bookkeeper: volity.game_record($record_id)
> Bookkeeper->Client: volity.game_record($record_id, $record)

I retain a preference for naming these RPCs differently. get_record and 
game_record? You're entirely right that they should deal with game 
records, rather than just the "history" data field.
(Continue reading)

Permalink | Reply |

Gmane