On Mon, 23 Mar 2015 13:22:00 +0200
Giulio Camuffo wrote:
> 2015-03-23 12:00 GMT+02:00 Marek Chalupa :
> > Destroyed seems confusing to me too, since the resource is not really
> > destroyed. What about inert or unalive ?
>
> Inert is ok, imho. On the client side they are called zombie
> objects.
On Tue, Mar 24, 2015 at 5:47 AM, Hardening wrote:
> Le 19/03/2015 09:11, Marek Chalupa a écrit :
> > When server looses some capability (like pointer or keyboard),
> > it takes some time to get this information to clients.
> > When client sends request with new_id argument to the object
> > that
Le 19/03/2015 09:11, Marek Chalupa a écrit :
> When server looses some capability (like pointer or keyboard),
> it takes some time to get this information to clients.
> When client sends request with new_id argument to the object
> that has been just destroyed on server-side (client
> does not know
On 03/23/2015 04:22 AM, Giulio Camuffo wrote:
2015-03-23 12:00 GMT+02:00 Marek Chalupa :
Destroyed seems confusing to me too, since the resource is not really
destroyed. What about inert or unalive ?
Inert is ok, imho. On the client side they are called zombie
objects... maybe for consistency
2015-03-23 12:00 GMT+02:00 Marek Chalupa :
> Destroyed seems confusing to me too, since the resource is not really
> destroyed. What about inert or unalive ?
Inert is ok, imho. On the client side they are called zombie
objects... maybe for consistency it'd be better to keep that here too.
>
> On
Destroyed seems confusing to me too, since the resource is not really
destroyed. What about inert or unalive ?
On Thu, Mar 19, 2015 at 2:34 PM, Bill Spitzak wrote:
> I think the name "intact" is really confusing. Can it be instead called
> "destroyed"?
>
>
> On 03/19/2015 01:11 AM, Marek Chalupa
I think the name "intact" is really confusing. Can it be instead called
"destroyed"?
On 03/19/2015 01:11 AM, Marek Chalupa wrote:
When server looses some capability (like pointer or keyboard),
it takes some time to get this information to clients.
When client sends request with new_id argument
When server looses some capability (like pointer or keyboard),
it takes some time to get this information to clients.
When client sends request with new_id argument to the object
that has been just destroyed on server-side (client
does not know about it yet), we still have to create the resource.
I
