On Tue, 2004-12-14 at 15:36 +0800, Gideon N. Guillen wrote:
Hi and thanks for all your answers.
> On Mon, 13 Dec 2004 20:10:35 +0200, Mika Raento
> <[EMAIL PROTECTED]> wrote:
> > 1. Multisync doesn't store a copy of the devinf from the device nor
> > request it. If the device doesn't send it (lik
On Tue, 2004-12-14 at 17:50 +0800, Gideon N. Guillen wrote:
> On Tue, 14 Dec 2004 11:39:01 +0200, Mika Raento
> <[EMAIL PROTECTED]> wrote:
> > Ah. But in this case we are a _server_, right? And transferring data
> > items to a 'device or database' sounds like keeping them around and not
> > just dr
On Tue, 2004-12-14 at 17:32 +0800, Gideon N. Guillen wrote:
> On Tue, 14 Dec 2004 10:29:56 +0200, Mika Raento
> <[EMAIL PROTECTED]> wrote:
> >
> > This is the only one I disagree with. The device explicitly sends a
> > 'Put' with its devinf, which in my understanding _is_ a request for the
> > ser
On Tue, 14 Dec 2004 11:39:01 +0200, Mika Raento
<[EMAIL PROTECTED]> wrote:
> Ah. But in this case we are a _server_, right? And transferring data
> items to a 'device or database' sounds like keeping them around and not
> just dropping them on the floor.
Not really, transferring does not necessari
On Tue, 2004-12-14 at 18:20 +0800, Gideon N. Guillen wrote:
> On Tue, 14 Dec 2004 12:02:00 +0200, Mika Raento
> <[EMAIL PROTECTED]> wrote:
> > Yes, so we should store the result of the Put we get, and not request
> > the devinf via a Get? The 7650 always sends a Put with the devinf when
> > connect
Hi
and sorry for the email barrage. Should have done some more testing
before sending the first ones. Now here's a list of some test results:
1. Multisync doesn't store a copy of the devinf from the device nor
request it. If the device doesn't send it (like a 7650 never does after
the initial co
