[haiku-web] Re: [Haiku] #11774: Investigate the potential of a web app store for HaikuDepot
- From: "richienyhus" <trac@xxxxxxxxxxxx>
- Date: Sat, 02 May 2015 09:48:56 -0000
#11774: Investigate the potential of a web app store for HaikuDepot
---------------------------+-----------------------
Reporter: richienyhus | Owner: haiku-web
Type: task | Status: new
Priority: normal | Milestone:
Component: Website | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
---------------------------+-----------------------
Comment (by richienyhus):
As for the web app, I'm not very convinced by the idea that we should
make a website our main way to discover native software. One of the
strength of Haiku is the tight integration of apps with each other, which
we currently can't provide with a web application. So, I would let
HaikuDepot (the native app) be the main way to discover and manage
software (no need for 2 separate apps when one will do). However, having a
way to show haiku apps to people not (yet) running Haiku would be nice. I
don't know if this is up to us or to the app developers.
Since the web app would also be getting all of its dynamic content from
HaikuDepot Server and it would let HaikuDepot Desktop handle software
management after the hpkg:// handshake, it would simply be providing an
alternative means of software discovery and filtering that would be
considered inappropriate feature creep if added to HaikuDepot Desktop.
This could equate to it only showing GUI apps, so that all libraries and
command line applications would be treated merely as dependencies that
HaikuDepot Desktop downloads along with the GUI application (after HDd
informs the user). Humdinger also came up with some unique filters for end
users on the mailing list.
There is also the problem that we desinged HaikuDepot and the package
system to work with multiple repositories, not just HaikuPorts. If that
works as planned, there would not be a single central website with all the
apps, but rather many sources of packages. In that case, HaikuDepot will
be able to gather the data from all package sources, but maybe a website
wouldn't.
This webapp would have a hard dependency on HaikuDepot Server. 3rd party
software repositories would either have to have their own HaikuDepot
Server installation, roll their own website with only static content like
Haikuware (but replacing download links with hpkg:// handshakes) or they
would need to get the repository added to the official HDS.
----
Replying to [comment:3 pulkomandy]:
What about OAuth, OpenID and friends for authentication?
That is perfectly fine for a single website, but they '''alone''' are not
sophisticated enough to create the infrastructure for a unified HaikuID.
Identity stacks simplify the maintenance of this infrastructure, such as
how Crowd provides a optional OpenID server, while on the other hand the
Open Identity Stack includes a server for the newer OpenID-Connect, LDAP
and more. It is basicly groupware but for highly scalable access, ID and
privilege management purposes.
For instance Andrew Lindesay has worked hard toward making sure HaikuDepot
Server is future proofed enough to be able to connect with any future
identity stack. This means you could safely use the same login for all
Haiku related websites (trac, drupal, pootle, HDS etc), as well as with
HaikuDepot Desktop and with any other desktop app.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/11774#comment:4>
Haiku <
https://dev.haiku-os.org>
Haiku - the operating system.
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts:
