[10:06:48 CDT(-0500)] * dmccallum (n=dmccallu@uni1.unicon.net) has joined ##uportal
[12:02:33 CDT(-0500)] * deuce (n=deuce@uni1.unicon.net) has joined ##uportal
[16:41:17 CDT(-0500)] * peterk_ (i=[U2FsdGV@66.226.77.81) has joined ##uportal
[17:18:55 CDT(-0500)] <deuce> peter?
[17:20:44 CDT(-0500)] <peterk_> hi Nick
[17:22:07 CDT(-0500)] <deuce> in what case(s) would a portlet get render request params if they are not targeted?
[17:22:47 CDT(-0500)] <peterk_> if the render param was set at any point earlier
[17:23:04 CDT(-0500)] <peterk_> the portal hangs on to the values and resends them at every request
[17:23:14 CDT(-0500)] <peterk_> that's in the spec (which was a surprise to me, I remember)
[17:24:30 CDT(-0500)] <deuce> hmmm .. but doesn't that mean that in those cases, the portlet will not be pulling from cache? because we explictly invalidate the portlet cache
[17:25:29 CDT(-0500)] <deuce> essentially .. if i click into a portlet, it will not ever pull from cache again?
[17:25:45 CDT(-0500)] <peterk_> no, won't pull from cache
[17:25:52 CDT(-0500)] <peterk_> but the render params are independent from cache
[17:25:52 CDT(-0500)] <deuce> that's bad
[17:26:12 CDT(-0500)] <peterk_> "not pulling from cache" upon interaction is in the spec too
Page Comparison
General
Content
Integrations