Michael Gauthier | 3 Nov 14:25 2010

Re: Proposal for a UUID package

On Fri, 2010-10-29 at 17:59 +0200, Mathieu Bruyen wrote:
> Hello all,

Hi Mathieu,

> I started to make some code about a package for generating UUIDs that
> I would like to publish in PEAR and I have some question about that.
> 
> I know that there is a PECL package doing that (
> http://pecl.php.net/package/uuid ) but here I propose a pure php-sided
> package. I know that in some way the php uniquid() function do the
> trick, but I propose to completely follow the RFC.
> My first question is: is it of interest?
> 
There's no harm in starting a proposal. I, for one, think it's a good
idea and would make a good PEAR package. This sounds like a good
proposal for PEAR.

> In more details my proposal consists of:
>  * An interface representing a Uuid. There are methods to get it as
> string, URN and raw (big)int because it is database friendly. This
> interface is implemented by different classes for the different
> variants. Right now I only plan to do the variant in RFC4122.
>  * An interface for a Uuid generator. It has two methods: creating a
> new Uuid and getting the variant of generated Uuids. There is one
> extending abstract class for the variant given in the RFC, which is
> itself declined into one abstract class for each Uuid version. These
> ones are defined because they expose an algorithm to subclasses (for
> example for version 1: getLock, getNodeId, getClockSequence, ...).
> Finally we have the real classes implementing the algorithms. Right
(Continue reading)

Mathieu Bruyen | 6 Nov 18:26 2010
Picon

Re: Proposal for a UUID package

On Wed, Nov 3, 2010 at 2:25 PM, Michael Gauthier <mike <at> silverorange.com> wrote:

> Hi Mathieu,

Hi

> There's no harm in starting a proposal. I, for one, think it's a good
> idea and would make a good PEAR package. This sounds like a good
> proposal for PEAR.

I just asked to know if there were was some other way that I didn't
know for generating them. I will continue to make it and make the
formal proposal when it will be what I expect it to be.

> The interface and features you describe sound great!

Thanks. I've done them thinking about extensibility.

> If you're looking for guidance on how to implement multiple backends, I
> advise you to look at the HTTP_Request2 package. The way HTTP_Request2
> works, it uses a default adapter class and you can set any other adapter
> class if you need to. This design works great for testing.

I was more thinking about having multiple generators and pick one at runtime.

Generators define some capacities: telling the parameters they
accept/require (a name, a size, ...) and some "tags" they have
(following RFC4122, creating unguessable UUIDs, being name-based,
...). The client calling the factory would define requirements (an
array of parameters, tags required) and the factory would pick one
(Continue reading)

Abhinav Singh | 8 Nov 23:34 2010
Picon

[PEPr] Proposal for XMPP::JAXL


Abhinav Singh (http://pear.php.net/user/abhinavsingh) proposes XMPP::JAXL.

You can find more detailed information here:
 http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Tim Jackson | 9 Nov 15:46 2010
Picon

HTTP_WebDAV_Server 1.0.0RC5 BC break; path confusion in different environments

Hi,

My colleagues and I have been successfully using HTTP_WebDAV_Server for a
long time and it generally works. One of the things we've always had to
work around is that versions up to 1.0.0RC4 looked for
$_SERVER['PATH_INFO'], which is not defined in many environments and seems
to be a rather historic way of doing things; according to
http://php.net/manual/en/reserved.variables.server.php it was for cases
where you had URLs like:

http://www.example.com/php/path_info.php/some/stuff?foo=bar

in which case PATH_INFO would be "/some/stuff"

In most modern environments many people (including us) just use something
like

RewriteRule /.*
/filesystem/path/to/some_front_controller_maybe_outside_the_docroot.php

and handle all the URLs in that front controller, in which case a request
for "/some/stuff?foo=bar" typically results in the following server
variables (these can also vary according to the use of mod_php vs CGI,
reverse proxies etc.; let's ignore that for now):

PATH_INFO is not defined
REQUEST_URI = /some/stuff?foo=bar
SCRIPT_NAME = /some/stuff

We always hacked around this by using a derived class of
(Continue reading)

Abhinav Singh | 12 Nov 13:02 2010
Picon

[PEPr] Changes in proposal for XMPP::JAXL


Abhinav Singh (http://pear.php.net/user/abhinavsingh) has edited the proposal for XMPP::JAXL.

Change comment:

Updated package description and package file link to current master at
github.

Please review the proposal:
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Michael Gauthier | 16 Nov 16:36 2010

[PEPr] Comment on XMPP::JAXL


Package source file is a 404 so I cannot review.

A high-quality XMPP library would be totally awesome for PEAR.

Quickly looking at the documentation the first change required for PEAR
acceptance is to make the file structure conform to PEAR's file structure
requirements.

The second is to use class constants instead of global constants.

-- 
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Abhinav Singh | 16 Nov 22:13 2010
Picon

[PEPr] Comment on XMPP::JAXL


Hi Michael,

Not sure why a 404 is returned for the pkg download link, shall update it.
Kindly download the source code from here:
https://github.com/abhinavsingh/JAXL

Will also look at PEAR code styling and see if anything what can be done to
make Jaxl PEAR compatible.

-- 
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Abhinav Singh | 16 Nov 22:15 2010
Picon

[PEPr] Changes in proposal for XMPP::JAXL


Abhinav Singh (http://pear.php.net/user/abhinavsingh) has edited the proposal for XMPP::JAXL.

Change comment:

Updated package link (previous link was throwing 404)

Please review the proposal:
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Till Klampaeckel | 18 Nov 17:58 2010
Picon
Picon

[PEPr] Comment on XMPP::JAXL


I just saw this proposal just now -- very cool stuff and certainly a great
addition to PEAR. :-)

Mike mentioned the preliminary things, let us know when they are done so we
can review more?

-- 
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Ken Guest | 18 Nov 19:16 2010
Picon

[PEPr] Comment on XMPP::JAXL


What Till said is an understatement at the very least...this is extremely
cool and I can't wait to use it.

-- 
http://pear.php.net/pepr/pepr-proposal-show.php?id=635

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


Gmane