MarcusSorealheis commented on PR #1479:
URL: https://github.com/apache/solr/pull/1479#issuecomment-1501064933

   > Please reach out if you need insight into current Admin UI. As you may 
know, Solr backend is 100% stateless, so there is no "login" as such. The 
current Admin UI will do the auth, caching Authorization header in browser 
storage, and pass in on all subsequent reqeusts to Solr backend.
   
   Will do for sure probably beginning this week as I think I've done 
sufficient research to have an opinion on the best approach. Haven't pushed it 
up yet but will very soon. I am aware of the backend being stateless.
   
   > Question: Is the goal still to host the entire Admin UI, including old 
non-ported angular-pages, from the new "modern" Admin App? Or do you plan to 
have two independent Admin apps and send users between them?
   
   I think the best approach is to host both the non-ported and ported UI's at 
the same time for a while. Given the scope and complexity, it will take some 
time for us to port over. I think the best path is to chip away at it here over 
the next 9 months until it is entirely ported over. Over time, I expecting 
porting to accelerate dramatically, and that estimate could be way overblown. 
There's also the fact that part of the decision I've chosen the framework that 
I have chosen is that it is extremely modern, seeing a lot of investment, and 
makes many strong choices about design. 
   
   I'm detailing the approach in a document for the next community meeting 
where people can review and comment, in addition to pushing up the example here 
shortly. The first example I started with was fine, but the framework and 
approach that was very popular for 6+ years is now obsolete. This approach is 
newer and should be good for another 6-10 years, which will be vital for 
preventing the situation that hit us more recently. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to