Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I like this idea. This is already available for Notes clients to get to internal Domino servers via the Passthru Use feature. You set up the external server through the corp firewall and then allow that first server to be a pass-through to the other back-end servers who are set-up to be allowed for pass-through destinations. It's on the right side of the Security tab of a all the Server documents. It is very easy to set-up and work great. Most of our mid-sized customers use this feature.
Agreed. We need to move away from endpoints needing to know the exact details of how the back-end is architected and how it changes over time.
The Notes client, for example, should never have to know anything more then this is where I go to find my "cluster". The server it ultimately gets directed to should be sorted dynamically behind the scenes.
This idea is very useful in the field of cloud hosting and docker. It allows automated and agile creation of Domino servers.
If, at the same time Notes would run in a browser (WebAssembly), there would be agility throughout the whole stack.
This feature is a quite important future-enabler.
[Toni Feric, Belsoft Collaboration]
Makes a lot of sense and is really important, also for Docker deployments!
Domino on Docker is one of the view applications that needs a separate IP, which is really a road-blocker in Docker infrastructure.
[ Daniel Nashed / http://blog.nashcom.de ]