On Feb 15, 7:50 pm, William Stein <[email protected]> wrote:
> +1 to the phone home idea
To elaborate a bit more on that, there are two methods. First, one
that just informs the user of a new release ("the current release is
<downloaded number>, but yours is <stored number>") - We only get
activity data on that certain page on the website, but since we don't
have the IP numbers, we have no idea how many different installations
are out there.
The enhanced method would be to append something unique after a "?"
sign to the URL. Personally, I have no problem with that and I know
that most of the major software packages do this. There is nothing
specific about the user sent and we do not have the IP.
We can start implementing method one and later decide if we upgrade to
method 2?
Additionally, it might be wise to append the client's current version
to the request url, so that we have an idea how outdated those sage
installations are. (i.e. http://www.sagemath.org/version.html?ver=4.3.2
)
Technically, the request should start asynchronous, in a separate
thread when sage is started - and joined with a short timeout when the
banner is displayed. Currently, my sage needs >10 secs to start and
the website has need 1.5 secs on average to respond.
H
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
