Comments (10)
Sure. The Buzz Client is capsuled by a doctrine-HttpCLientInterface. So we can just replace Buzz by a common doctrine HTTP client. Perhaps we could start with the interfaces we are currently building and add methods which you (and others) think that needs to be added to be a common doctrine interface. Later then we could move it to the common part.
from search.
like i said .. imho we can wait until you are closer to having a working and semi finished search API done ..
from search.
Why not adopt Buzz if that is okay with Kris ?
from search.
i think the scope Doctrine Common isn't to provide an http client that can do it all. But I do think its a good idea to keep the out of the box dependencies as small as possible. So I am sure in the end our HTTP client will not have all the features of Buzz, but will provide a good out of the box experience.
from search.
Yes. Then lets start to define the Doctrine HttpClientInterface.
Mike Lohmann
0171 270 4156
Am 11.11.2011 um 08:41 schrieb Lukas Kahwe Smith
[email protected]:
i think the scope Doctrine Common isn't to provide an http client that can do it all. But I do think its a good idea to keep the out of the box dependencies as small as possible. So I am sure in the end our HTTP client will not have all the features of Buzz, but will provide a good out of the box experience.
Reply to this email directly or view it on GitHub:
#22 (comment)
from search.
I'd be happy to write an adapter and tests to integrate Guzzle with the HttpClientInterface.
from search.
Hi,
It would be nice to have an other client supporting the client interface.
At a first view the Guzzle-Http-Client brings much functionality we
perhaps don't need. If you want to implement it with the current
interface it can be used but I don't see it as the common http client.
Imho we should find the requirements for a common http-client first.
Then design the interface.
I agree to Lukas and think we should wait a little more, until we have
a basic functionality working. Perhaps we than have a deeper
understanding of what we really need in the client and can define a
interface suits our needs.
What do you think?
2011/11/11 Michael Dowling
[email protected]:
I'd be happy to write an adapter and tests to integrate Guzzle with the HttpClientInterface.
Reply to this email directly or view it on GitHub:
#22 (comment)
from search.
I agree. I think it's a good idea to create an HttpClientInterface
for common and provide a simple implementation that covers most use cases. I am saying that if you want adapters for HTTP clients after this interface has been created, then I can create an adapter for Guzzle.
from search.
Ah. Cool. :)
2011/11/11 Michael Dowling
[email protected]:
I agree. I think it's a good idea to create an
HttpClientInterface
for common and provide a simple implementation that covers most use cases. I am saying that if you want adapters for HTTP clients after this interface has been created, then I can create an adapter for Guzzle.
Reply to this email directly or view it on GitHub:
#22 (comment)
from search.
The current elastic search is using elastica. I think this can be closed.
from search.
Related Issues (20)
- Support for root object type mapping
- Support for Update API HOT 3
- Use filtered queries instead of setFilter() in ElasticSearch client
- Remove implementation of ZendLucene
- Neo4j support? HOT 2
- Refactoring annotations into more specific 'types' HOT 1
- Implement XML mapping support
- FOSElasticaBundle overlap? HOT 3
- Are there any contributing guidelines ? HOT 1
- Specifying the index HOT 7
- Status updates? HOT 3
- The annotation does not exist, or could not be auto-loaded. HOT 1
- Get `hits` for the query HOT 1
- Project still alive? HOT 4
- Delete from Query, Elastica dependencies. HOT 2
- Add support for "attachment" type
- Add support for "ip" type
- Can I use Doctrine Paginator with the Search query HOT 9
- Support for "null_value" field attribute
- Support for "term_vector" field attribute
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from search.