refactor route provider example

[ElectricMaxxx]

Q	A
Doc fix?	yes
New docs?	no
Applies to	all
Fixed tickets	#421

So...
started to refactor the example for the route provider. It isn't ready. Got some open issues:

• just injecting the document manager instead of the document registry cause it is a very specific
  example?
• adding the service config for yml and php
• little refactorings in text

[ElectricMaxxx]

merge into master should be right in here or? It's stuff that needs to go online directly, right?

[wouterj]

It's stuff that needs to go online directly, right?

Indeed, it's not a feature, it's a "doc fix" so it should be merged into master

[wouterj]

Symfony solution (the whole sentence doesn't look correct)

[dbu]

why "endpoint"?

[ElectricMaxxx]

this was the name in the old example.

[dbu]

lets just call this thing acme_demo.route_provider

[ElectricMaxxx]

All comments of @dbu shows me, that i should have discuss a little more in the issue. It is hard to create an example of a thing that is simple in general, but can be implemented in so many different use cases. We should ask: What would be the "cmf example". I would say it should contain the cmf route and the part of setting the document.
Problem for creating something on the fly would be, that we have to explain why to return a RouteCollection. So we need to create more than one Route (reason for the candidates thing).

[dbu]

we can simply return a collection with just one element. and say that if your logic would support route parameters, you could end up with more than one candidate.

to me, the point of this example is how to use the DynamicRouter with something else than PHPCR or ORM which are already provided in the bundle. its more a case of: "you don't need to implement your own Router, if you want to load routes on request and the only thing that is different is how you load those routes." now for a good example, i really don't know. everything based on orm / phpcr will be difficult to make the point. maybe a route provider with elasticsearch? quite involved again... still better than doctrine mongodb as at least elasticsearch returns us arrays and is not an object-mapper, so we could create the routes from the elasticsearch information...

[lsmith77]

ping

[ElectricMaxxx]

Pong.

Will be back this evening. Delayed that one here.

[dbu]

should we still do this or do you want to port a light version with just some tweaks into a new PR?

[ElectricMaxxx]

👍 for doing a light example.

[dbu]

@ElectricMaxxx ping (sorry, guess you get a couple of emails today, i am wading through old github issues...)

[dbu]

shall we close this?

[wouterj]

Feel free to start a new one when you have time, @ElectricMaxxx