I don't like this idea. Perhaps I'm one of those privacy-minded people
since we use Tapestry in a security sensitive context (credit cards).
I remember some time ago when we looked at upgrading Quartz and were
surprised to see the new version trying to dial home in a similar manner
(by default)
Update checker, added in 1.7.2
http://jira.opensymphony.com/browse/QUARTZ-842
An option to turn it off, added in 1.8:
http://jira.terracotta.org/jira/browse/QTZ-29
Not so funny when this unnecessary feature introduces new bugs:
http://jira.terracotta.org/jira/browse/QTZ-28
To me, adding a feature like this communicates to users that the
library/framework in question is not meant to be used in an "enterprise"
environment since nothing like this would get past QA (at least not where
I work)
On Mon, 11 Oct 2010 18:49:13 +0200, Howard Lewis Ship <hls...@gmail.com>
wrote:
What would be the repercussions if Tapestry included a start-up filter
that "reported" the application startup back to some central location,
so that we could get some idea of where and how Tapestry is being
used? Obviously, this would be documented, in such a way that it
would be easy to turn off for the privacy-minded.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
