When you do switch to port 80, please send an email to those that have
requested email updates from your project.
jm7
Nicolás Alvarez
<nicolas.alvarez@
gmail.com> To
Sent by: [email protected]
boinc_dev-bounces cc
@ssl.berkeley.edu
Subject
Re: [boinc_dev] Problems on adding
09/06/2009 09:34 one more URI for current project
PM
El Dom 06 Sep 2009 21:59:09 Kunsheng Chen escribió:
> Hi everyone,
>
> My boinc project is currently using non-default port number instead of
port
> 80.
>
> All the configurations in config.xml are complying with the current port.
>
> I am wondering if it would cause any problem if I add another port
> directing to the same place but keep the original one (For example, I add
> URI:80 as a default project URI for future new users but keep URI:8005
for
> current users and all previous settings in config.xml ). Would it be a
> problem for the new users in the future ? Synchronization and
application
> signatures are the mainly two issues I concern about.
You cannot have more than one master URL for a project. The master URL is
the
identifier for your project. You can, however, have multiple scheduler
URLs,
or multiple download URLs for each file.
If you want to use port 80, then switch to it completely.
Changing a project URL is not a trivial task. Each app_version, workunit
and
result in the database has the URL. Usually it's easier to let all current
work get processed, then change config.xml and generate new application
versions. In any case, users *will* have to detach and reattach.
--
Nicolas
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
