I am currently integrating this sdk with our product. I have received an error today that I have 0 credits and "license expired". I have never processed a page. Yesterday the images were queued for a long long time and never processed. I think this sdk has great potential. Some suggestions:
1.) health check method - you may have this already, please post a method to determine the status of the service. I would rather not process my customers documents or put them in the queue if the service is down.
2.) queue wait time - there appears to be some latency between submission and actual processing. If we had an estimated wait time, it might be better for my users to determine if they want to process or wait.
3.) account information - you may have this already, if my customers want information about how many "credits" are left in their account, this would be helpful.
Again, this looks like a promising sdk. Thanks.
asked 01 Jul '12, 18:27
You were affected by the ABBYY Cloud OCR SDK service failure occurred yesterday.
Corrective and Preventive measures taken by ABBYY Cloud OCR SDK team
Please be assured that system reliability is a top priority at ABBYY, and we are making continuous improvements to make our service the best on the web.
Sincerely yours, Alsu. ABBYY, Marketing manager, SDK products.
PS: This was the first serious failure since the service started its work on Feb, 2012 (Public Beta).
answered 02 Jul '12, 18:10
We encourage you to use UserVoice for feature request submission and voting for them. It will help us to prioritize feaure request better way (there is always long list of things you know you should do, but you have to prioritize anyway).
Few suggestions according your requests
1) We are struggling hard to make sure service has near to 100% uptime, but this is the cloud world, and outages happens even for long time established players like Google and SalesForce. Hoewever, it is easy to check if service is up - if it responds to requests then it is up. But what you are trying to solve is to check if queue is short enogh - that is different story. We are not going to provide public access to overal system queue length, since it is a security hole. We are taking different approach. What we are implementing is priorities management, so even if queue is filled by tasks from one customers, others are not affected. It is partially implemented, but not perfect yet. This is still high priority task for us, and you will be able to see improvements quite soon.
2) There is special parameter in response format specifically for that purpose - estimatedProcessingTime. Currently it is more like a placeholder, but making it real it is not very far in our roadmap.
3) I can imagne different scenarios.