[ghns] Renewed collaboration among data sharing frameworks

[Sebastian Pösterl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Josef Spillner schrieb:
> > Hi all,
> >
> > we recently found out that a GHNS-style functionality for GNOME
exists, thus
> > reinforcing the charter of the GHNS project at freedesktop.org.
> >
> > It's the NewStuffManager:
> > 	http://www.k-d-w.org/index.php?page=newstuffmanager
> > and its author has subscribed to this list already - welcome Sebastian!
> >
Hi Josef!

> > We're already quite far with the next generation KNewStuff2
implementation on
> > the KDE side, but interesting features can still be added. What's more
> > important to me personally is that the format of information on the
wire (as
> > per our current GHNS spec) can be considered generic enough, or
whether there
> > need to be changes.
> >
You're XML file specification is very good.

In addition, I have some questions to clarify that I understand the
concept correctly. On the server runs a Webservice and the client
connects to it. Is the client a desktop application (KNewStuff I guess)
or a webpage? Does the Webservice also handle up/downloading or does it
just present data? And what do I need to do to setup such a service?

> > KNewStuff2 doesn't have any relationship to D-BUS at the moment. If
we want to
> > unify things on this level as well, it would also be on topic for
this list.
> > So far I haven't seen a compelling argument for D-BUS in this area
though.
> >
I dont' know if D-Bus makes sense in your case, because the goals GHNS
and NSM want to achieve are quite different. GHNS wants to provide a
platform that makes it easy to share documents (e.g. wallpapers,
pictures, PDFs). Therefore, it's aimed to make a end-user's life easier.

On the other hand, NSM is aimed to be used by developers. The idea is
that many applications have plugins but only some have a mechanism to
update or download additional plugins easily. Therefore, I want to
provide a framework to make it easy for developers to equip their
application with a plugin update mechanism. The NSM daemon runs on the
user's computer. Whereas the developer has to upload a XML file that
contains a list of plugins to a server. In this context using D-Bus
makes perfectly sense, because the developer should be free to choice a
language. All in all, the end-user should not even recognize that NSM
even exists.

I think you're project is really cool and fits perfectly in the web 2.0
world, but I hope that I could make it clear that the only common
property is that both download stuff. Therefore, I don't think it would
be that easy to merge both projects or adjust one to another.

- --
Greetings,
Sebastian Pölsterl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGI4O91ygZeJ3lLIcRAhPmAKCNFGuasiyXpdwzPvMly59Xy1cFZQCfbzvt
gm1bC4Zpb5CYn6AVnrYQyu4=
=y1nA
-----END PGP SIGNATURE-----