Re: Query on Message size limit

garet.cammer@premiereglobal.com — Fri, 04 Sep 2009 17:54:47 GMT

There are no rigid limits to the SOAP message size or the number of documents that can be sent in a single JobSubmit. We do not impose a timeout via our web service, although other external components of the system (proxy servers, etc) may impose limits.

However, there are some Best Practices that we recommend. Since the larger the message, the longer it will take to send and to process, there is little advantage to including more than one document set / destination set per JobSubmit. That is, if you have separate documents to separate destinations, it is best to create separate JobSubmits. They have a better chance of getting distributed in parallel, therefore shorter delivery times.

If you give us some more details about your application, with some specific numbers and possible trade-offs, we can be more specific in our recommendations.

Query on Message size limit

diarmuid.linehan@aspiracon.com — Fri, 04 Sep 2009 17:33:03 GMT

Hi,

Typically what is the upper limit of SOAP message size (e.g. for JobSubmit) supported by PG Messaging API?

Also, are there any more specific limitations in terms of the constituents of a request?

E.g. in the case of a JobSubmit Request where CFS-stored files are referenced in the DocumentSet, is there a specific limit on number of files that can be referenced and/or on number of Message elements contained in the SOAP message?

Thanks in advance,
Diarmuid

PGiConnect: Message List - Query on Message size limit

Re: Query on Message size limit

Query on Message size limit