[Digikam-devel] list of possible GSoC projects for digikam

[Marcel Wiesweg]

> >   Note: I don't know  how this feature could affect core digiKam
> >   database stuff.
> >
> >   http://bugs.kde.org/show_bug.cgi?id=146865
> >
> > - Off-line manager
> >
> >   http://bugs.kde.org/show_bug.cgi?id=114539
>
> Mik, this can be done ony when new DB schema + DB interace will be
> finalized by Marcel. It's too short to propose an GSoC about this subject.
>
> But i'm agree with you, this feature is very important to do for the
> future...

Yes. This requires too parts:

- adapt database backend to a database system (say, MySQL, or PostgreSQL) that 
supports running on a server with multiple client access. This mostly 
involves checking that our SQL, which is developed for SQLite, also works for 
the other db. "Real backend" stuff like client lib access is done for us by 
Qt

- set up locking mechanisms and change notifications needed when two people 
access the same image / album / tag structure at the same time. (currently, 
there is code to distribute change notification via DBUS locally). This could 
be done by mechanisms of the database, an extra client/server structure, peer 
to peer approach, or a combination of these.