You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by RO...@usbank.com on 2002/10/09 19:34:34 UTC
Transfer
Can I transfer say a 20 M file via soap? If so how do I wrap that and
should I be even considering
SOAP for such a transfer?
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Transfer
Posted by Scott Nichol <sn...@scottnichol.com>.
The base64-encoded data compresses pretty nicely with gzip, though.
Scott Nichol
----- Original Message -----
From: "Skip Marler" <sm...@parasoft.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 2:31 PM
Subject: Re: Transfer
> You can attach the file within the SOAP envelope, but, it will use
encoding.
> I can't give the exact calculation but for every 6 bytes you want to
send
> you actually send 8.
>
> Regards,
> Skip Marler
>
> www.parasoft.com
> smarler@parasoft.com
> ----- Original Message -----
> From: <RO...@usbank.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, October 09, 2002 10:34 AM
> Subject: Transfer
>
>
> > Can I transfer say a 20 M file via soap? If so how do I wrap that
and
> > should I be even considering
> > SOAP for such a transfer?
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > For additional commands, e-mail:
<ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Transfer
Posted by Scott Nichol <sn...@scottnichol.com>.
The base64-encoded data compresses pretty nicely with gzip, though.
Scott Nichol
----- Original Message -----
From: "Skip Marler" <sm...@parasoft.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 2:31 PM
Subject: Re: Transfer
> You can attach the file within the SOAP envelope, but, it will use
encoding.
> I can't give the exact calculation but for every 6 bytes you want to
send
> you actually send 8.
>
> Regards,
> Skip Marler
>
> www.parasoft.com
> smarler@parasoft.com
> ----- Original Message -----
> From: <RO...@usbank.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, October 09, 2002 10:34 AM
> Subject: Transfer
>
>
> > Can I transfer say a 20 M file via soap? If so how do I wrap that
and
> > should I be even considering
> > SOAP for such a transfer?
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > For additional commands, e-mail:
<ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Transfer
Posted by Skip Marler <sm...@parasoft.com>.
You can attach the file within the SOAP envelope, but, it will use encoding.
I can't give the exact calculation but for every 6 bytes you want to send
you actually send 8.
Regards,
Skip Marler
www.parasoft.com
smarler@parasoft.com
----- Original Message -----
From: <RO...@usbank.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 10:34 AM
Subject: Transfer
> Can I transfer say a 20 M file via soap? If so how do I wrap that and
> should I be even considering
> SOAP for such a transfer?
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Transfer
Posted by Skip Marler <sm...@parasoft.com>.
You can attach the file within the SOAP envelope, but, it will use encoding.
I can't give the exact calculation but for every 6 bytes you want to send
you actually send 8.
Regards,
Skip Marler
www.parasoft.com
smarler@parasoft.com
----- Original Message -----
From: <RO...@usbank.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 10:34 AM
Subject: Transfer
> Can I transfer say a 20 M file via soap? If so how do I wrap that and
> should I be even considering
> SOAP for such a transfer?
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Transfer
Posted by Scott Nichol <sn...@scottnichol.com>.
Reasons you might want to use SOAP:
1. You want to process the document as soon as it is received
2. You want the sender to know the result of the processing
3. You want to write as little plumbing as possible
Here's what I would do in a couple situations
1 = don't care, 2 = no, 3 = yes
I would use FTP or SSH (if more security is required).
1 = yes, 2 = don't care, 3 = don't care
I would send the document using HTTP POST and write a simple servlet
1 = yes, 2 = yes, 3 = yes
I would use SOAP, which would have the additional benefit of providing a
standard way to document the service if I needed third parties to
interface with my processor. For ease of coding, I would pass the
document as a parameter (see the Apache SOAP mime sample for code that
does this). I definitely would use a nightly build of Apache SOAP so
that I could enable gzip encoding, so the document would be compressed
on the fly.
Scott Nichol
----- Original Message -----
From: <RO...@usbank.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 1:34 PM
Subject: Transfer
> Can I transfer say a 20 M file via soap? If so how do I wrap that and
> should I be even considering
> SOAP for such a transfer?
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Transfer
Posted by Scott Nichol <sn...@scottnichol.com>.
Reasons you might want to use SOAP:
1. You want to process the document as soon as it is received
2. You want the sender to know the result of the processing
3. You want to write as little plumbing as possible
Here's what I would do in a couple situations
1 = don't care, 2 = no, 3 = yes
I would use FTP or SSH (if more security is required).
1 = yes, 2 = don't care, 3 = don't care
I would send the document using HTTP POST and write a simple servlet
1 = yes, 2 = yes, 3 = yes
I would use SOAP, which would have the additional benefit of providing a
standard way to document the service if I needed third parties to
interface with my processor. For ease of coding, I would pass the
document as a parameter (see the Apache SOAP mime sample for code that
does this). I definitely would use a nightly build of Apache SOAP so
that I could enable gzip encoding, so the document would be compressed
on the fly.
Scott Nichol
----- Original Message -----
From: <RO...@usbank.com>
To: <so...@xml.apache.org>
Sent: Wednesday, October 09, 2002 1:34 PM
Subject: Transfer
> Can I transfer say a 20 M file via soap? If so how do I wrap that and
> should I be even considering
> SOAP for such a transfer?
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>