How do you verify the size of a large ( 32K) plain text body

Question

Hello All,
I am running GW 8.0.2 Hot Patch 3, using SOAP schema 1.04.
When I attempt to process a message, that contains only a plain text body with a size (in bytes) of 64,382 - the following sizes are reported by objects extracted from GroupWise, via SOAP calls:
Message Size: 71,425 (should be bigger than the plain text body).
Message Part [0] length: 70,854 - no idea where this value comes from
In the getAttachmentResponse object, the part has:
length: 87,772 - Which matches the Base64 encoded length, plus padding, of the plain text.
The actual size of the plain text (on disk): 64,382
I am hoping to use the HTTP GET method for extracting the large plain text object, which means that I will not have access to the getAttachmentResponse object.
So my question is, based on the MessageBody, MessagePart[0] length of 70,854 - is there a formula, or other way to determine the correct expected byte size of the plain text object to enable me to verify that the HTTP GET operation or the SOAP getAttachmentRequest completed correctly?
Regards,
Dave Stiller.

Answer 1

Hey Preston,
Thanks for the prompt response. Not the answer that I was seeking, but none the less an answer. Thanks.
Can I suggest an enhancement for a future release, to add an additional structure to the message object that allows you to detail the available formats and byte sizes of the formats that relate to the message body object. This could even be an extension/completion of the MessagePart object array on the Message Body. (One array component for each available format.) There are no issues when dealing with large body texts as attachments, but an accurate byte count is important to me.
This will enable us to verify that the message body content, downloaded from GroupWise, has not be corrupted during transfer - particularly important when using HTTP requests.
Have a great day,
Dave...
Originally Posted by Preston Stephenson
You will have to be careful in getting message bodies.
The plain text message body can come from different
sources and / or formats.
The message body can be stored in RTF format.
You can extract the plain text from the RTF text.
If there is a text.htm message body attachment, the
GW Client will extract the text plain text from the
text.htm attachment and will ignore the text plain
message body attachment.
There can be corruptions in the message body
attachment. The attachment can report a certain
size, but the actual data may be different.
You have to assume what is stored / returned is
correct. If you are bound and determined to read
the number of bytes recorded, you can cause
problems. There was one case where the attachment
was corrupt. The POA returned all the data that
was available. The application tried to read past
the end of the valid data and caused the POA to
crash.
You get all of the data in one HTTP GET call. In
that case, the "Content-Length" header will have
the number of bytes in the message body attachment.
Preston
>>> On Sunday, August 12, 2012 at 11:36 PM,
stillerd<[email protected]> wrote:
> Hello All,
>
> I am running GW 8.0.2 Hot Patch 3, using SOAP schema 1.04.
>
> When I attempt to process a message, that contains only a plain text
> body with a size (in bytes) of 64,382 ‑ the following sizes are
reported
> by objects extracted from GroupWise, via SOAP calls:
>
> Message Size: 71,425 (should be bigger than the plain text body).
> Message Part [0] length: 70,854 ‑ no idea where this value comes from
>
> In the getAttachmentResponse object, the part has:
> length: 87,772 ‑ Which matches the Base64 encoded length, plus padding,
> of the plain text.
>
> The actual size of the plain text (on disk): 64,382
>
> I am hoping to use the HTTP GET method for extracting the large plain
> text object, which means that I will not have access to the
> getAttachmentResponse object.
>
> So my question is, based on the MessageBody, MessagePart[0] length of
> 70,854 ‑ is there a formula, or other way to determine the correct
> expected byte size of the plain text object to enable me to verify that
> the HTTP GET operation or the SOAP getAttachmentRequest completed
> correctly?
>
> Regards,
> Dave Stiller.