Paul Mossman wrote: > Hi all, > > I'm looking at XCF-3152, which asks for HTTP access to phone profiles. > > Possibly we'd want to go with HTTPS as well, depending on how much SSL > certificate pain it causes. > > Either way, is a new Jetty "web application" the best approach? > >
Do you know that we already use http to server SNOM profiles? You may want to have a look at how it's done. As for using jetty to serve profiles through http: there is really no compelling reson for it and there are factors against it: - servlet container (such as jetty) is not best suited to for serving static files (such as device configuration) - it can be made to do that but configuring it is not going to be as easy as configuring dedicated http server (we currently use apache, lighthttpd might be an option here - although once we stop hijacking apache I see no reason to give it up) - generating profiles should be isolated from serving profiles: currently sipXconfig generates profiles, and apache, vftp, ttpd servers are serving the profiles - ideally provisioning server does not even have to run on the same machine as sipXconfig: if that's the case you can safely upgrade or switch off sipXconfig without affecting profile delivery D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
