updated Readme and Handled Typeerror on query-server

[gabru-md]

Readme.md has been updated with the latest trends. It did not have the &num=10 mentioned before.
query-server now returns a errorObject in JSON Format whenever 500 error_code is encountered, so that the page is not left stuck.

Fixes #142 and #140

Image for corresponding change:

[AnshulMalik]

Shouldn't we put some efforts to actually fetch the result, why we get the error code 500 at the first step?

This looks like a workaround to me.
How about making the query successful instead of showing error?

[gabru-md]

@AnshulMalik you are very right.
But a 500 error is generally caused when a client sends a lot of requests to the server. I know it because I've studied DOS and DDOS. Server instead of responding to them just ignores them as it configures all those requests to be spam/traffic. (if I'm not wrong)
So there is nothing that we can do on our/query-server's side to resolve this error. 500 error_code response is sent from Google's server to our script.
Please check this page for more info : https://www.lifewire.com/500-internal-server-error-explained-2622938

[AnshulMalik]

@gabru-md Ok. But I am pretty sure google isn't returning 500 response. It's caused by query-server while parsing response from google.
Can you please debug it a little?

[gabru-md]

@AnshulMalik is your PR solving this problem ?

[AnshulMalik]

Yes @gabru-md, it does. Meanwhile, I am trying to generate a demo link.

[gabru-md]

But then it is not generating the required number of results or is it ?

[gabru-md]

@AnshulMalik I believe that your PR is not a fix to the pertaining problem. Since it is defying the very purpose of &num=10 . Therefore I believe it is better to display an error object fot the time ,while we can discuss upon the fact on how to resolve the issue without altering the number of results asked for.
What do you say on this ? I'll be happy to discuss and solve this. :D

[mariobehling]

Ok, let's iterate from here. Cheers.