Comparison API choking on a comparison

GroupDocs.Comparison Product Family
1

Hi there,

I was told that a response of “Postponed” meant that there was an error handling the comparison with 2 docs. Can you investigate the responseobject below (you can get the docs from the guids inline) and tell me what went wrong with this comparison?

Thanks!

Greg Herrington

GetJobDocumentsResponse Object
(
[result] => GetJobDocumentsResult Object
(
[job_status] => Postponed
[inputs] => Array
(
[0] => JobInputDocument Object
(
[status] => Processed
[proc_date] => 1363035896400
[output_formats] => docx
[outputs] =>
[job_errors] => Array
(
)

                                [actions] => Compare
                                [supported_output_file_types] => 
                                [name] => Memorandums of Understanding[Fellers & Herrington, LLP (greg.herrington)][version no. 108].docx
                                [version] => 1
                                [size] => 813507
                                [type] => Words
                                [type_str] => Words
                                [file_type_str] => Docx
                                [document_path] => Memorandums of Understanding[Fellers & Herrington, LLP (greg.herrington)][version no. 108].docx
                                [access] => Private
                                [url] => https://api.groupdocs.com/v2.0/shared/files/db0505e58b1f026a6c53e84eecdbe51c131a5ebd2a8c17ac0154b054c2a7e70b
                                [file_type] => Docx
                                [id] => 49418
                                [guid] => db0505e58b1f026a6c53e84eecdbe51c131a5ebd2a8c17ac0154b054c2a7e70b
                            )

                        [1] => JobInputDocument Object
                            (
                                [status] => Processed
                                [proc_date] => 1363035896400
                                [output_formats] => docx
                                [outputs] => 
                                [job_errors] => Array
                                    (
                                    )

                                [actions] => Compare
                                [supported_output_file_types] => 
                                [name] => Memorandums of Understanding[Fellers & Herrington, LLP (greg.herrington)][version no. 109].docx
                                [version] => 1
                                [size] => 813148
                                [type] => Words
                                [type_str] => Words
                                [file_type_str] => Docx
                                [document_path] => Memorandums of Understanding[Fellers & Herrington, LLP (greg.herrington)][version no. 109].docx
                                [access] => Private
                                [url] => https://api.groupdocs.com/v2.0/shared/files/9157b7c4306596c5b9c781f4f33e3aa9822411b4db6deb4757afed98f328d9dc
                                [file_type] => Docx
                                [id] => 49446
                                [guid] => 9157b7c4306596c5b9c781f4f33e3aa9822411b4db6deb4757afed98f328d9dc
                            )

                    )

                [outputs] => Array
                    (
                        [0] => JobOutputDocument Object
                            (
                                [error] => 
                                [name] => 
                                [version] => 0
                                [size] => 0
                                [type] => Cells
                                [type_str] => Cells
                                [file_type_str] => Docx
                                [document_path] => 
                                [access] => Private
                                [url] => 
                                [file_type] => Docx
                                [id] => 0
                                [guid] => 
                            )

                    )

            )

        [status] => Ok
        [error_message] => 
        [composedOn] => 1363035923884
    )

Submitted from: https://www.groupdocs.com/

2

Hi Greg,

We checked compare API with your files and all works well. You can check this here with our PHP SDK Sample (Doc for this sample - http://groupdocs-php-samples.herokuapp.com/docs/sample19.html). Our dump results are almost the same, exept job_status field (public 'job_status' => string 'Archived' (length=8). Could you please check if you use the last version of PHP SDK? Also you can try to use some delay before request results (like we do in our sample above).

Please notify us if the issue was resolved or if you need any further help with this.

Many thanks,
Vipin Thomas, GroupDocs Support Team.

3

Hi,

My comparisons typically work fine....this has only happened a couple of
times. The couple that have choked the system in the past were in fact
identified as problem documents by Derek and I think he escalated the
support to Aspose to fix whatever was wrong with the handling of those
documents..... so I assumed that this was a similar issue.

I have a 2 second delay between polling attempts (max time frame of 30
seconds) in this particular case that I can't use the job callback for.

I am using the latest version of the SDK and it was actually my earlier
support request that identified the bug in 1.2.4 that is now reflected in
1.3.1 / dev-master. (the continue/break issue on line 316 of APIClient.php)

I've already looked at the sample and it is useful to understand the SDK,
but is not a production quality approach -- the callback approach or a
polling approach is what I've been using.

If you want me to increase the time period between polls, I'm certainly
willing to do that, but the current intervals I'm don't seem to have been
a problem so far. To be clear, I am not continually polling without a
sleep() call if that's what you;re worried about.

Also, please clarify for me what the "Postponed" response means; I'm going
to assume from your that you're hinting that it occurred b/c my polling
intervals were overloading something .... like i said, in the past, Derek
told me that meant the documents themselves were the problem whenever I got
"Postponed", so please just let me know if that's not the case how I should
handle any such responses in the future.

Thanks, Greg