Skip to content

discovery doc #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dbu opened this issue Aug 23, 2015 · 2 comments · Fixed by #4
Closed

discovery doc #1

dbu opened this issue Aug 23, 2015 · 2 comments · Fixed by #4

Comments

@dbu
Copy link
Contributor

dbu commented Aug 23, 2015

while reading the current discovery doc, i wonder whether the "discovery" class needs to be in a specific namespace or anything or if its automatically discoverd. or are only guzzle 5, 6 and dactilos automatically discovered and other adapters must be registered manually to be found?

@sagikazarmark
Copy link
Member

Discoveries are some sort of registries of different components (message implementations, adapters) supported by us. Every adapter which we create will land in the HttpAdapterDiscovery. Every other major implementation (like a PSR-7 one) will get into the Message discovery. Any other custom stuff must be manually registered.

This is not the best solution, but I couldn't come up with anything better which allows zero-configuration.

sagikazarmark added a commit that referenced this issue Aug 23, 2015
restructure discovery documentation - Fix #1, Fix #2
@dbu
Copy link
Contributor Author

dbu commented Aug 23, 2015 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants