Poo-tee-weet

Re: State of PHPCR

Auke van Slooten — Tue, 15 May 2012 16:42:26 +0200

I live in enschede, which is about 2 hours away by car from Amsterdam, so its not exactly next door... also I'll be on holiday untill june 9th so I don't think I'll get much work done on phpcr and ariadne in the mean time. Let's see how it goes :)

Query parameter handling in Symfony2

Lukas Kahwe Smith — Sat, 12 May 2012 16:02:25 +0200

So this topic has been going back and forth in my head a lot over the last months: how do we best handle query parameters in Symfony2? Obviously you can already access query parameters today already but it could be easier. Essentially what I want is a way for developers to easily configure what query parameters they expect and what values they expect. This is useful for several things like easier reading and validating of query parameters, self documenting API both for API docs for humans but also for machines. Now thanks to Alexander we have a solution that works. But there is the big question if this is really the right approach. For now ignore the fact that it only works with annotations for now, because that is fixable. But it does point to the question if this shouldn't be integrated into the routing configuration itself by adding query support for our implementation of uri-templates.

While this at first seems like the right place for this sort of configuration, it raises the questions of its own since path parameters (i.e. /{foo}) should be handled differently than query parameters (i.e. /{?bar}). For one I don't think that a mismatch on a route requirement of a query parameter cause the route to not match. However then it can quickly become confusing for the end user or it would require adding more and more syntax to handle all the different cases.

Feedback much appreciated!

Update: I have just merged the change to FOSRestBundle.

Re: State of PHPCR

Lukas Kahwe Smith — Sat, 12 May 2012 11:19:31 +0200

@Auke one thing to note is that PHPCR/Jackalope is Apache licensed which is incompatible with GPLv2. It is compatible with GPLv3 however. See the recent discussion on the PHPCR users mailing list.

Re: State of PHPCR

Lukas Kahwe Smith — Fri, 11 May 2012 16:10:17 +0200

Ok cool .. I will be in Amsterdam for http://www.windmillwindup.com/2012/ .. I will be quite busy .. but depending where you are located exactly .. we might be able to meet just to say hi at least.

Re: State of PHPCR

Auke van Slooten — Fri, 11 May 2012 15:15:39 +0200

Well, started to create a phpcr implementation around Ariadne's store, but it's not going to be pretty. One of the things is that Ariadne hasn't migrated to namespaces yet. Fortunately the store is first on our list to refactor and update to PHP 5.3 and namespaces.

For now I'm rather hacking the thing together, learning the structure of the API as I go. Not sure how far I'll get :)