Stories
Slash Boxes
Comments

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Friday May 02, 2008
03:06 AM

Data::UUID::Base64URLSafe

[ #36311 ]

I've just released Data::UUID::Base64URLSafe:

Data::UUID creates wonderful Globally/Universally Unique Identifiers (GUIDs/UUIDs). This module is a subclass of that module which adds a method to get a URL-safe Base64-encoded version of the UUID using MIME::Base64::URLSafe. What that means is that you can get a 22-character UUID string which you can use safely in URLs.

Of course, only afterwards do I notice Data::GUID::URLSafe. What is the point of a Globally/Universally Unique Identifier if we don't have a unique name for the concept, eh?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Yeah, there was a two-fold problem. One: Data::UUID is unclearly licensed, and the author has been unreachable, so far. Two: the Data::UUID interface is unpleasant (to me). So, rather than make Data::UUID::Licensed or Data::UUID::Simple or something, I just used the other (and more common in my experience, anyway) name. I tried to make some hubbub about this when I did so, but obviously I was not able to really make sure everyone saw Data::UUID get a thbbt.

    Maybe I should change its abstract on the CPAN.
    --
    rjbs