On Thu, Jul 9, 2009 at 8:00 AM, Tomeu Vizoso wrote:
> On Mon, Jul 6, 2009 at 16:33, Eben Eliason wrote:
>> On Mon, Jul 6, 2009 at 10:02 AM, Sascha
>> Silbe wrote:
>>> On Mon, Jul 06, 2009 at 12:29:53PM +0200, Tomeu Vizoso wrote:
>>>
Agreed. I have to say that your proposal is excellent, congra
On Mon, Jul 6, 2009 at 16:33, Eben Eliason wrote:
> On Mon, Jul 6, 2009 at 10:02 AM, Sascha
> Silbe wrote:
>> On Mon, Jul 06, 2009 at 12:29:53PM +0200, Tomeu Vizoso wrote:
>>
>>> Agreed. I have to say that your proposal is excellent, congratulations!
>>
>> Thanks, I'm flattered. :)
>>
>>
Is th
On Mon, Jul 6, 2009 at 16:02, Sascha
Silbe wrote:
> On Mon, Jul 06, 2009 at 12:29:53PM +0200, Tomeu Vizoso wrote:
>
>> Agreed. I have to say that your proposal is excellent, congratulations!
>
> Thanks, I'm flattered. :)
>
>
>>> Is the asynchronous API design useful enough to warrant more complex
>
On Mon, Jul 6, 2009 at 10:02 AM, Sascha
Silbe wrote:
> On Mon, Jul 06, 2009 at 12:29:53PM +0200, Tomeu Vizoso wrote:
>
>> Agreed. I have to say that your proposal is excellent, congratulations!
>
> Thanks, I'm flattered. :)
>
>
>>> Is the asynchronous API design useful enough to warrant more comple
On Mon, Jul 06, 2009 at 12:29:53PM +0200, Tomeu Vizoso wrote:
Agreed. I have to say that your proposal is excellent,
congratulations!
Thanks, I'm flattered. :)
Is the asynchronous API design useful enough to warrant more complex
implementation?
I'm not sure, but I think that whatever decisi
On Sun, Jul 5, 2009 at 22:32, Sascha
Silbe wrote:
> Hi!
>
> After reading the recent threads about Journal / data store and the IDs used
> by them the big picture is much more clear now, thanks!
> I've adjusted by datastore redesign proposal [1] accordingly and would like
> to submit it for review
6 matches
Mail list logo
