Groups > Borland > Dellphi web services soap > Re: TSOAPAttachment that's not streamed...partial success.




Re: TSOAPAttachment that's not streamed...partial success.

Re: TSOAPAttachment that's not streamed...partial success.
Fri, 21 Mar 2008 07:50:04 +010
On Thu, 20 Mar 2008 17:03:24 +0100, Jean-Marie Babet <bbabet@borland.com> 

wrote:

> I'll need to look at the code to confirm but (to be consistent with the  
> rest
> of the framework), in 'Client' mode you're responsible for all cleanup:

I am not talking about freeing the attachment, but telling the framework  
not to use it any more.
I am freeing the attachment immediately after the web service call. It  
just didn't feel good, since I did not tell the framework that there's no  
attachment any more. That's what my question is aimed at.

As there are not references to freed objects, I reckon that the framework  
notices that. Or clears the attachment list by itself.

Thanks for your reply,
Post Reply
Re: TSOAPAttachment that's not streamed...partial success.
Mon, 24 Mar 2008 15:35:51 -080
Thank you for the clarification.

Unfortunately (or fortunately for your case), the framework does not hold on
to headers across calls. This is something that has been requested but not
yet implemented. So you basically constantly have to set the header(s) for
each and every call - something that's tedious if you're talking to a
service that requires a particular header with the same data for every call.

Such a service would be something like eBay. One has to set the same header
across each call (in the case of eBay there's a slight tweak to URL's
callname=xxxx parameter in the URL querystring but that's not related to the
RequestCredentials header). This is unfortunately as it's inefficient. I'm
looking forward to having some time to remedy.

Cheers,

Bruneau.

Post Reply
Re: TSOAPAttachment that's not streamed...partial success.
Tue, 25 Mar 2008 10:40:50 +010
On Tue, 25 Mar 2008 00:35:51 +0100, Jean-Marie Babet <bbabet@borland.com> 

wrote:

> Thank you for the clarification.
>
> Unfortunately (or fortunately for your case), the framework does not  
> hold on
> to headers across calls. This is something that has been requested but  
> not
> yet implemented. So you basically constantly have to set the header(s)  
> for
> each and every call - something that's tedious if you're talking to a
> service that requires a particular header with the same data for every  
> call.
>
> I'm
> looking forward to having some time to remedy.

If you do, where's the place I could clear the headers properly now (with  
the unstreamed attachment implemented that adds itself to the attachment  
list in objecttosoap)?

Thanks so much for your prompt help,
Post Reply
Re: TSOAPAttachment that's not streamed...partial success.
Tue, 25 Mar 2008 16:20:48 -080
Hello,

Maybe I need to see the context of the call but I would assume that you can
clean any headers after the call to the service returns. Let me know if it's
more complicated that this [it typically is :(].

Cheers,

Bruneau.

Post Reply
about | contact