Re: Hidden Meta Information

[aric lasry]

Hey Michael.
This is a good point but we don't handle that and even if I already
had the need for something like that when I was using other API, I
always found another (better) solution
I don't think this is the job of the API. More over how can you be
sure that it's not another client / device that wrote these datas ?

On Mon, Feb 13, 2012 at 4:08 PM, Michael <michael_...@hotmail.com> wrote:
> Hi,
>
> is there a possibility to store custom meta information with an object
> which is not shown to the user?
>
> There are two reasons for doing this:
> 1. when a client calling the api has a problem with processing the
> response and could not identify the refernece ID to a created object,
> this gives a possibility to identify the object during later
> synchronisation.
> 2. custom functionality of the client could be realised without
> impacting the functionality of the web app or any other client.
>
> Thanks,
> Michael

--
Aric LASRY | Co-founder & Lead dev @Producteev.com | 00 (1) 646 705
1274 | New York City

[Michael Mueller]

thanks for your reply! I would be looking forward to your better solutions
;-)

I see the point in not knowing which client the information belongs to but
this could be handled by tagging the information with some unique client ID.
The scenario that currently worries me is that I am implementing a mobile
client and reliability of the connection is low. In this case, a request for
creating a task might have been sent to the server but the response is lost.
Now the client is off for a while and the user changed the task on the
server already. Getting back online, what would I do with the pending task
to create? I have no possibility to identify that the task on the server is
related to the one on the client. I would like to avoid to create useless
data or let the user solve the issue, this would be a bad UX in my opinion.

/Michael