David Golden wrote:
I install Test::Reporter on any machine I administer, so that as I
install perl modules, their success or failure gets reported. Now I'm
getting emails asking me to use HTTP. I'm trying to follow them, but
am hitting roadblocks, and am wondering why I'm jumping through hoops
to fix what seemed to be working fine from my perspective.
Hi, yary. Thanks for writing with your questions. The switchover to
HTTP based submission was prompted by the perl.org administrators, who
were getting nearly half a million test reports by email -- accounting
for about 99% of monthly email traffic to perl.org mailing lists.
Since more and more people were having trouble with email submission
due to restrictive firewalls and ISP's, the second generation
transport is HTTP.
Unfortunately, due to the haste of the switch and the limited
volunteer time to write documentation and code to automate the
conversion, there is still a good deal of manual work to do.
Just a thought about default behavior.
Wouldn't it be better if Test::Reporter would use File transport by default? T::R::T::File itself can print some message
offering to install T::R::T::Metabase and set it up.
I also think of failover mechanism, which can be implemented using T::R::T::File as a backup transport, when there's
some problem with submission to Metabase.
--
Serguei Trouchelle
