GSOC 2008: A new service

Alex Kosenkov alex.kosenkov at gmail.com
Tue Mar 25 11:48:04 UTC 2008


Hello, Nikolaj.

Just in case resending to amarok at kde.org and btw alongside I can develop
support of Ampache and it's missing functionalities.

I'll make a proper application for the second proposal about xmms2 etc.
soon.

---

Yeap, you did get it right. Those parts about Ampache that you wrote are
also correct.

And yes, communication of other amaroks will be very complicated task. And
it's realization includes something more than just Ampache. It can be a
daemon along side with Ampache and it'll act through it's own protocol. And
the goal is not to just share the content of amaroks between users, but in
the same time to make download process from server a lot quicker using the
content of the nearest amarok. Also users will be able to download some of
the content from Ampache even if it's down. So the benefits are obvious and
I'd be happy to contribute this functionality under GSOC ;)

Also I have another proposal about Amarok - nowadays everybody invents a
bicycle using different GUI for services such as xmms. mpd etc. And a lot of
my friends who uses stuff like that would like to have an ability for Amarok
to communicate with such services (playing directly through it, geting
playlists, album-pictures) through their API. The idea is to make an Amarok
service a client-layer for those services.

I submited my proposal to KDE category, I hope to be able to do my best ,)
---



2008/3/25, Nikolaj Hald Nielsen <nhnfreespirit at gmail.com>:
>
> Hi Alex
>
> Thanks for your proposal.
>
> If I understand your proposal correctly, what you want to achieve is
> basically to allow Amarok to fetch its content from a server, as well
> as from other instances of Amarok. Is this correct?
>
> With regards to the server, we already have the Ampache server service
> which can accomplish much of what you want to achieve. Also, there is
> a proposal to add up and download functionality to the Ampache
> service, so that will go some way to achieve what you wish.
>
> As for allowing different running Amaroks to share content, this goes
> way beyond what the service framework is currently capable of and
> would likely be a very large project in its own right. If this is
> something you want to explore, you should write our mailing list at
> Amarok at kde.org so the other developers can also give their opinions.
>
> Also, please look at http://code.google.com/soc/2008/ for some
> information about writing and submitting proposals. Proposals for
> Amarok goes in the KDE category.
>
> Feel free to mail me any question, but I will also see your mails if
> you send them to amarok at kde.org, and as others will be able to answer
> you there as well, the replies will likely be quicker! .-)
>
>
> - Nikolaj
>
>
> On Tue, Mar 25, 2008 at 11:31 AM, Alex Kosenkov <alex.kosenkov at gmail.com>
> wrote:
> >
> >
> > Hello there, I want to introduce my ideas about Amarok: adding a new
> > service.
> >
> >  This can be completely outstanding feature of Amarok amongst all other
> > players.
> >
> > Basically, I don't like usual approach to store all audio data on local
> > hard-drives, yeah it is kind of stable, but in this case a lot of space
> on a
> > hard-drive is just wasted and very often work with hd becomes a
> bottleneck
> > for hardware. But now we have an Internet. Especially when we have a
> local
> > network - it's much more effective to store the whole data on a specific
> > server, which will be manipulating all the data (basically it is the
> > unix-like approach to do things - make each separate detail do it's own
> work
> > and polish it). And MORE: we can make an ability for users to
> collaborate
> > with each other even when the main server goes offline. And I can make
> these
> > features as flexible as it's possible.
> >
> >
> > See details in attachment.
> >
> > --
> >
> > Best regards, Alex Kosenkov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20080325/f0ef0209/attachment.html>


More information about the Amarok mailing list