]
Steven Hawkins updated TEIID-250:
---------------------------------
Component/s: Salesforce Connector
Fix Version/s: 6.1.0
Affects Version/s: 6.0.0
Complexity: Low
Enable Axis data compression in SFDC Connector, per SFDC API
guidelines
-----------------------------------------------------------------------
Key: TEIID-250
URL:
https://jira.jboss.org/jira/browse/TEIID-250
Project: Teiid
Issue Type: Feature Request
Components: Salesforce Connector
Affects Versions: 6.0.0
Environment: MetaMatrix 5.5.2 with patch 0037/SFDC GA connector
Reporter: Greg Haber
Assignee: John Doyle
Fix For: 6.1.0
The SFDC doc includes a set of performance guidelines for using their API
(
http://blog.sforce.com/sforce/2005/04/performance_tip.html). One of the guidelines:
Use compression, unless you have an OC45 connection into the back of your machine,
compression will help reduce transmission times, the Sforce API supports gzip and deflate
compression for both request and response.
does not look like it has been implemented in our connector. In theory, this will be a
big optimization when returning large data sets, as is the case at Genentech. This is
also a trivial optimization to implement, so we should at least try this out and see what
the impact is.
The process for enabling this is described on
http://wiki.apexdevnet.com/index.php/Compression_with_Axis_1.3 - essentially, you subclass
the SforceServiceLocator class in the salesforce.jar to set a few Axis-specific properties
(complete code for subclass is at the link), and then in our connector (in ConnectionImpl)
we call this subclass instead of calling the SforceServiceLocator directly, as we are
doing today.
This is a very low hanging fruit with a big upside - please implement soon.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: