Re: [Evolution-hackers] improve PHOTO support in libebook/EDS

[Patrick Ohly <patrick ohly gmx de>]

On Thu, 2011-07-07 at 15:09 +0530, Chenthill wrote:
> I like the staging directory approach. Would it be possible for
> implementing the logic to convert the inline data ->file inside 
> e_book_client_add_contact so that the clients need to worry about
> changing the code ?

"need *not* worry", right?

Yes, I can imagine that this would work. Should we allow to enable or
disable this client side? In other words, should we force the separate
storing of photo data in all cases or is there a legitimate situation
where a client might want to force the data to be stored inline?

I can't think of one myself.

Note that once we introduce this mechanism (whether it is mandatory or
not), all clients must be prepared to deal with PHOTO URIs. But this is
not new, because there might already be contacts in current EDS with
URIs.

The only change would be that clients get an URI for their *own*
contacts even if those had inline data.

-- 
Bye, Patrick Ohly
--  
Patrick Ohly gmx de
http://www.estamos.de/