Refactor suggest implementation to more closely resemble query implementation
Fix \Elastica\Suggest\Phrase for php 5.3 compatibility
Using GET instead of POST seems to make it work
Expanded change description. Replaced \Elastica\Query::addSuggest() with \Elastica\Query::setSuggest() for consistency
Merge branch 'master' of git://github.com/ruflin/Elastica into suggest-refactor
Merge pull request #510 from jlinn/suggest-refactor

Refactor suggest implementation
Use query parameter for optimize calls, add refreshAll
Merge pull request #516 from liip-forks/fixing-optimize-functions

Using GET instead of POST seems to make it work
Fix returning of suggestion results in \Elastica\ResultSet
Merge pull request #517 from jlinn/suggest-refactor

Fix returning of suggestion results in \Elastica\ResultSet
Send scroll_id via HTTP body instead of as query param

Elasticsearch scrolling queries can accept `scroll_id` either as a query
parameter or as the raw HTTP body. The Elastica should always pass the id
via HTTP body for safety.

The Elasticsearch `scroll_id` is a base64 encoded value that appears to be
a serialized string that contains key/value pair data for each shard in
the cluster. As the number of shards grow the size of `scroll_id`
increases proportionally. In addition by default Elasticsearch caps URLs
at 4kb as governed by the `http.max_initial_line_length` setting.

Thus as the size of a cluster grows at some point all scrolling queries
will fail if passed via the query parameter.

Conflicts:
	changes.txt
Add tests for sending scroll_id via HTTP body

We are only testing that `scroll_id` will be sent via HTTP body instead of
via query param. (See thread in #518)
Merge pull request #519 from xyu/scrollid-in-body

Send scroll_id via HTTP body instead of as query param
Fix TypeTest by running optimize after creating new type to make sure it exists
Merge branch 'master' of https://github.com/ruflin/Elastica