Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too much generalization for apps? #39

Open
lukasbestle opened this issue Nov 11, 2013 · 1 comment
Open

Too much generalization for apps? #39

lukasbestle opened this issue Nov 11, 2013 · 1 comment

Comments

@lukasbestle
Copy link
Member

After reading http://decentralize.it again, I realized the idea of providing each app with its own CouchDB instance/subdomain/inbox email address might be a bit too generalized.

Not every app will be a web server/web app but instead maybe a Jabber/XMPP server.
These do not require different subdomains as different servers run on different ports.
Also, not every app needs a CouchDB database but maybe a MySQL database instead.

Maybe, we should offer an API to let each app request access to specific core features (subdomains, email addresses, databases, ports) and they will be provided to them as soon as the user accepts this - I don't think giving every app a set of features from the beginning is required.
Forcing the apps to be accepted by the user will also make sure an app can't collar 1000 different ports other apps might need. Instead, the user would have to accept that "the app wants to register a Jabber/XMPP server" (automatic mapping of standard ports) or something like that.

@augustl
Copy link
Contributor

augustl commented Nov 11, 2013

Tere is some additional discussion around app run-time here: #33

It seems that we're converging on docker.io?

Sent from my smartphone.

Lukas Bestle [email protected] wrote:

After reading http://decentralize.it again, I realized the idea of providing each app with its own CouchDB instance/subdomain/inbox email address might be a bit too generalized.

Not every app will be a web server/web app but instead maybe a Jabber/XMPP server.
These do not require different subdomains as different servers run on different ports.
Also, not every app needs a CouchDB database but maybe a MySQL database instead.

Maybe, we should offer an API to let each app request access to specific core features (subdomains, email addresses, databases, ports) and they will be provided to them as soon as the user accepts this - I don't think giving every app a set of features from the beginning is required.
Forcing the apps to be accepted by the user will also make sure an app can't collar 1000 different ports other apps might need. Instead, the user would have to accept that "the app wants to register a Jabber/XMPP server" (automatic mapping of standard ports) or something like that.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants