no option to drop apache in lieu of a lighter weight web server using neoconf? or does that need to wait until tapestry is altogether gone?
On Fri, Oct 22, 2010 at 4:09 PM, George Niculae <[email protected]> wrote: > On Fri, Oct 22, 2010 at 3:08 AM, Douglas Hubler <[email protected]> wrote: > > This spec also solves a number of other very important pieces like > > allowing for other web technologies to be introduced. > > > > http://wiki.sipfoundry.org/display/xecsdev/Web+Service+API+Unification > > > > Here is what I think we should investigate about web architecture > migration: deploy a SSO server that supports various SSO clients > (java, rails, python, etc.) together with sipxconfig, then add neoweb > project (with same look and feel as current UI) under SSO umbrella and > refer pages from current UI. At some point in future maybe drop > altogether the Tapestry part. > As a SSO server CAS looks very good, JOSSO can be also an option here. > > George > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
