[erlang-questions] inets service startup

[Serge Aleynikov]

Ingela Anderton Andin wrote:
> [...]
>> I was poking around through inets code, and there turns out to be an 
>> option in httpd.erl for starting httpd service by hooking it up to a 
>> custom supervisor (httpd:start_link/1).  This seems to solve the second 
>> problem I had of being able to separate a critical httpd service from 
>> the other ones managed by inets.
>>   
> Well yes there is such an option,  starting it this way however will 
> make the http-server part
> of your application instead of the inets application and you can for 
> instance no longer utilize soft upgrade for the inets application. 

I might be wrong with the resulting conclusion, yet it seems to me it 
should work.  In order to start an httpd instance this way, it would 
still require inets to be started.  Given that if you make your custom 
application that owns the httpd instance dependent on inets (i.e. 
include inets in the 'applications' section of the *.app file), wouldn't 
release handler be able to do a soft upgrade of inets by restarting your 
custom app together with the httpd instance?  Or this wouldn't classify 
as a truly soft upgrade?

Serge