[Owncloud] OwnCloud - Question about fetching favicons in bookmark section
jon at sprig.gs
Tue Aug 30 12:52:27 UTC 2011
How about this for a favicon workflow?
1) Download favicon. It's the first time it's been used, store it as
www.example.com.0.ico and add that favicon to the database.
2) Second person adds a bookmark in www.example.com. Download the
favicon, and then diff it against each of the dns-named favicons which
have been downloaded - currently only www.example.0.ico - if it's the
same, delete the downloaded favicon and re-use www.example.com.0.ico
in the database. If it's not the same store it as
3) User deletes their bookmark which is the last instance of
www.example.com.0.ico. System deletes www.example.com.0.ico from the
Jon "The Nice Guy" Spriggs
On 30 August 2011 13:42, Arthur Schiwon <blizzz at arthur-schiwon.de> wrote:
> Hey Golnaz,
> On Tue, 30 Aug 2011 16:34:55 +0430, Golnaz Nilieh
> <golnaz.nilieh at gmail.com>
>> Hi Arthur,
>> I'm working on favicon support in bookmark section of owncloud.
> thanks for working in this! :)
>> It works almost well, but I need to consult you about a question:
>> For each bookmark, I get a .png image from http://g.etfv.co/ , and save
>> somewhere for later use.
> Do you have further information about this service, e.g. is it free /
> which is the licence? Basically this makes sense, of course, to keep
> Internet traffic low.
>> At first I created data/favicons/ folders inside bookmark/ folder, but
> we I
>> think they should be saved outside the application directory, somewhere
>> the main data/ folder.
>> But every user has a directory corresponding to his/her username there,
>> creating a favicon/ folder there may cause conflicts.
>> What's your opinion?
> I think we can decouple favicons from user-specific bookmarks, in order to
> not redundantly store multiple favicons of the same webpage. Therefore
> another table in the database can be established (that was my first
> thought). I would not like to save files in the user file system - this
> should be only for files the user moves, modifies and deletes. I.e. i favor
> the solution inside the bookmarks app directory. Since it is beneficial to
> have all data at one (or fewest possible) place – alone for easier backups
> – I'd go with the database solution.
> Two things to consider:
> - Theoretically web sites can have different favicons on different pages
> (esp. sub domains), but as few as possible should be stored
> - Also in my mind are thumbnails of web pages, so when designing the
> storage solution it should be flexible enough to be expanded for another
> ccing the ML, maybe there are further opinions?
> Owncloud mailing list
> Owncloud at kde.org
More information about the Owncloud