Subdomains support in content server (webapps server). #1082
Conversation
| return "DIRECT"; | ||
| }} | ||
| "#, | ||
| DAPPS_DOMAIN, path.host, path.port); |
There was a problem hiding this comment.
only one DAPPS_DOMAIN? would probably be sensible to have a .parity domain for inbuilt-parity stuff (which would use parity-specific RPCs) and .dapp domain for theoretically standardised, cross-implementation stuff.
There was a problem hiding this comment.
It can be easily extended to support more "domains", but we can still use addresses like:
http://status.parity.dapp or http://myoracle.ethcore.dapp
There was a problem hiding this comment.
yeah; i'm taking direction from the classic about: (and newer chrome:) protocols which don't try to map over http: but rather use a different namespace.
i would reserve the .dapp domain for pages/packages which are, in principle, independent of parity. .parity could be used for our packages which are built in (i.e. all of them at present).
There was a problem hiding this comment.
Updated the domain to .parity (since we only have built-in dapps).
Will prepare multi-domain support in separte PR.
gavofyork
added
A6-mustntgrumble 💦
tomusdrw
added
A0-pleasereview 🤓
gavofyork
added
A8-looksgood 🦄
No description provided.