| Subject: | wurfl_home does not work as document |
| Date: | Mon, 16 Mar 2009 16:44:20 +0100 |
| To: | bug-Mobile-Wurfl [...] rt.cpan.org |
| From: | Jonas Pasche <jonas.pasche [...] skytel.de> |
The documentation says:
=item wurfl_home
Used to set the default home diretory for Mobile::Wurfl. This is where the cached copy of the wurfl.xml file is stored. It defaults to current directory.
This is not true for the current version of Mobile::Wurfl. In fact, all
functions use $self->{wurfl_file}, which does not honor the wurfl_home
setting. Only the location of the logfile is changed with wurfl_home.
In fact, even the name "wurfl.xml" is not used under all circumstances.
$self->{wurfl_file} is derived from $self->{wurfl_url} and takes the
last part of the string as the filename.
Finally, using the included update/get_wurfl methods is deprecated
according to the WURFL website as of 2009-03-16:
CHANGE IN WURFL DISTRIBUTION MECHANISM! Pay ATTENTION! This is a
rather large change which may impact some deployed applications.
The SourceForge guys are unhappy with members who use the web
space to release large files. They have even established a
mechanism which will throttle the download speed of large files
(such as current wurfl.xml). For this reason, newer wurfl.zip
snapshots are now released the SourceForge way by relying on SF
standard package release procedure.
Unfortunately, using the SF release procedure, wurfl.xml isn't available
through a static URL. To keep it simple, using CVS as the download
source for wurfl.xml would possibly be the most simple solution.