Hello,
I see that "Accept-Encoding: identity" is sent in the request headers when getting data for the XmlaDataSource. So, IIS compression cannot be applied to the HTTP response. Does XmlaDataSource support gzip or deflate encoding?
I think that enabling compression for text/xml responses can really improve performance of PivotGrid.
Thanks & Regards,
Alex
PS: I'm talking about version v.11.1
Can someone from Infragistics please reply to this question? We are performing an evaluation on the PivotGrid to determine if we are going to move forward. The availability of IIS compression will play a role in our decision.
Thanks,
Chad
Currently we haven’t support for gzip and deflate. The reason is that we are using client HTTP handling in order to provide an authentication on the client. Supporting this functionality in the context of the client HTTP handling means that we need to read the compressed data on our own, which is not covered now. We will consider to implement such functionality in some of the future releases.
Best regards.
PPilev.
I was thinking as fast and painless to expose to the end user a some callback mechanism where it have to provide its own processing of the compressed data. Another way to work around is to give you an option to specify how to handle the HTTP requests. Then if you have chosen a web browser handling and you still need an authentication, you have to type your credentials in the browser’s dialog box. I think it wouldn’t take a long time for implementation but it still needs to be tested, so I’m not sure when we can deliver it. We agree that is very important feature and my advice in this case is to contact our developer support team so they can open a feature request for you and then we can prioritize the tasks for the next release or service release.
Plamen.
Plamen,
Thank you for your answer.
I see that there is an open issue in Microsoft. But it seems this is not resolved in Silverlight 5.
https://connect.microsoft.com/VisualStudio/feedback/details/575037/provide-support-for-gzip-deflate-compression-when-using-silverlight-client-network-stack
Is it possible to prioritize this improvement for the XmlaDataSource? I'm also performing an evaluation on XmlaDataSource and performance is critical in my application.
Best Regards,