This behavior is wrong, as the API returns the completion status for a validation job in a RESTful fashion: in particular, the HTTP 202 (Accepted) status code means the API consumer should reissue the request later (see http://verifalia.com/developers/email-validations#getting-status). Apart from compliance to the API specification, this behavior can cause issues if the API consumer expects to actually find its validation results whenever the SDK marks a validation job as completed.
The EmailValidations class incorrectly marks a validation job as completed if the noOfCompletedEntries is equal to noOfTotalEntries:
https://github.com/verifalia/verifalia-ruby-sdk/blob/master/lib/rest/email_validations.rb#L88
This behavior is wrong, as the API returns the completion status for a validation job in a RESTful fashion: in particular, the HTTP 202 (Accepted) status code means the API consumer should reissue the request later (see http://verifalia.com/developers/email-validations#getting-status). Apart from compliance to the API specification, this behavior can cause issues if the API consumer expects to actually find its validation results whenever the SDK marks a validation job as completed.