Can i ask why exactly your looking at this ?

The documentation states that it accepts batch requests up to 1MB so
why are you checking the size before posting ?

There only so much the API will do for you but building a solid system/
app relies on checks on both ends.

Tom Wilson
Freelance Google Base Developer and Consultant
www.tomthedeveloper.com

Google Base Tools - http://dev.tomthedeveloper.com/googlebase
Featured Project : 
http://google-code-featured.blogspot.com/2008/02/google-base-competitor-analysis.html


On Dec 11, 11:28 pm, icebackhaz <[email protected]> wrote:
> Trying to see what happens when one stuffs too much into the xml
> payload, we have discovered that there is no facility for detecting
> the exact problem either before or after the send.
>
> The repsonse from the server is  HttpURLConnection.HTTP_BAD_REQUEST.
> It looks like the intension was to generate a InvalidEntryException
> and that looks bogus too, but at least the getReason() might be useful
>
> Unfortunately the built-in second attempt to send the payload chokes
> big time and we get a java.io.IOException from deep in Sun's code and
> the 401 floats off into the either.
>
> I've sent the to the bugs forum, but not sure it will be recognized as
> a bug:http://code.google.com/p/gdata-issues/issues/detail?id=921
>
> This is further compounded by the fact that even if we hadn't been
> blown out of the water there is no access to the httpRequest which has
> the all important header: "Content-Length"  (This has been recognized
> as a 
> bug:http://code.google.com/p/gdata-issues/issues/detail?id=742&sort=-id&c...)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Base Data API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Base-data-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to