Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

[12:25:23 CDT(-0500)] <obbo> hello, i am seeing an issue with webproxy portlet. i have a small page that is displayed in the portlet and the page has a couple screens that you can navigate through via ajax. that is working fine and the links all work but after a while of navigating between each screen, the portlet begins to slow down and it takes longer and longer to navigate between screens

[12:26:17 CDT(-0500)] <EricDalquist> unless the ajax is written in a very specific way it will not work with the proxy portlet

[12:26:31 CDT(-0500)] <EricDalquist> as the portlet has no way to intercept the ajax calls and route them through the portlet

[12:26:59 CDT(-0500)] <obbo> i'm pretty sure it is being written correctly as i am able to use it through the portlet

[12:27:02 CDT(-0500)] <EricDalquist> http://jasig.275507.n4.nabble.com/data-ajax-returns-does-not-display-data-within-webproxy-portlet-td4355777.html

[12:27:28 CDT(-0500)] <EricDalquist> as for the slowness

[12:27:28 CDT(-0500)] <EricDalquist> O

[12:27:37 CDT(-0500)] <obbo> just that the first few interactions with the portlet work fine but after that it starts to slow down

[12:27:38 CDT(-0500)] <EricDalquist> I'm not sure what would be the cause without more info

[12:27:47 CDT(-0500)] <EricDalquist> can you tell which step is getting slow?

[12:27:54 CDT(-0500)] <EricDalquist> like is it the client side js

[12:28:07 CDT(-0500)] <EricDalquist> or the actual ajax request handling?

[12:28:47 CDT(-0500)] <obbo> are you able to view the ajax requests handled by the portlet with chrome's dev tools?

[12:29:11 CDT(-0500)] <EricDalquist> yeah, browser side they don't change at all

  • No labels