[mashup-dev] Defualt HTTP & HTTPS ports to be used in the Mashup Server

[Jonathan Marsh]

I'd say go ahead with 8762 and 8443 for now, and let's file a post-alpha
JIRA to capture the other options listed here.

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: mashup-dev-bounces at wso2.org [mailto:mashup-dev-bounces at wso2.org]
> On Behalf Of Thilina Gunarathne
> Sent: Tuesday, May 29, 2007 12:43 AM
> To: mashup-dev at wso2.org
> Subject: Re: [mashup-dev] Defualt HTTP & HTTPS ports to be used in the
> Mashup Server
> 
> Sanjiva Weerawarana wrote:
> > If we want to get complicated .. there's a nice solution:
> Well.. I was just worried about the scenario where mashup server and
> WSAS running on the same machine, cause still we are using the same
> ports as WSAS.
> 
> I feel like getting complicated is definitely post alpha1.. How about
> shipping the alpha1 with something looks similar to the WSAS ports.
> Eg: 8762 & 8443
> 
> Thanks,
> Thilina
> >
> > - if on windows check whether IIS is running and auto install
> ourselves
> > under that using the IIS installation stuff we have for WSAS
> >
> > - if on linux or an similar with apache httpd do similarly
> >
> > - if otherwise (e.g., someone on linux is using thttpd on 80) then
> fail
> > or default intelligently to port 8080 or 9762 or something else.
> >
> > - DOCUMENT THIS BEHAVIOR CLEARLY!
> >
> > Sanjiva.
> >
> > Jonathan Marsh wrote:
> >> 80 would be nice, if I wasn't also running a web server (that will
> screw
> >> things up won't it?)  I expect most of our customer base will
> already be
> >> running a web server, and using the mashup server to augment their
> >> offerings
> >> with Web Services.
> >>
> >> Is finding the best ports something that an installer could check
> and
> >> help
> >> with?
> 
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev