[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Soap Variable Limited to 32767 Bytes Length in HTTP API
Ups
it wasn't meant that way.
This morning I was attenting a small meeting on SCION/DTU (Danish
Technical University) where we�
actually�discussed the mental barriers that are in receiving large
amounts of data via web services�
directly�into the application instead of receiving them as a file
which the user then feel they can import�
themself giving them a false sence of control.�
This is for us an increasing problem in cloud-based solutions
On Thu, Jun 7, 2012 at 10:10 PM, Bob P. Roche
<[1]BRoche@xxxxxxxxxxxxxxxxx> wrote:
� Scott didn't say it was large for sending actual data. Just it
seemed
� large for sending the SoapAction.
� >sending +32 K isn't unusually if you replace traditional EDI
� (EDIFACT/X12)
� >with a
� >XML based web service communication or you send a file in JSON in
� order to
� >respond to a AJAX call
� >On Thu, Jun 7, 2012 at 8:53 PM, Scott Klement
<[2]sk@xxxxxxxxxxxxxxxx>
� wrote:
� >> Thomas,
� >>
� >> 32k seems excessively large for SoapAction! �SoapAction only
� indicates
� >> the action to take, it doesn't actually carry any data... � �Do
we
� >> really need to be able to exceed 32k for it?
--------------------------------------------------------------------
---
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[3]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
--
Regards,
Henrik Rützou
� [4]http://powerEXT.com
� [plogofull200.png]
References
1. mailto:BRoche@xxxxxxxxxxxxxxxxx
2. mailto:sk@xxxxxxxxxxxxxxxx
3. http://www.scottklement.com/mailman/listinfo/ftpapi
4. http://powerext.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------