[09:09:29 CDT(-0500)] <Arvids> hey, EricDalquist
[09:09:41 CDT(-0500)] <EricDalquist> good morning/evening Arvids
[09:09:49 CDT(-0500)] <Arvids> 
[09:09:58 CDT(-0500)] <Arvids> I wanted to ask regarding AJAX portlets
[09:10:12 CDT(-0500)] <Arvids> is https://wiki.jasig.org/display/PLT/AJAX+in+a+Portlet still applicable to v4.0?
[09:10:37 CDT(-0500)] <Arvids> I'm trying to figure out the basic architecture for translation portlet
[09:10:38 CDT(-0500)] <EricDalquist> no, in 4.0 just use the Resource support in the portlet 2.0 spec
[09:10:55 CDT(-0500)] <Arvids> i've no experience with it 
[09:10:55 CDT(-0500)] <EricDalquist> that approach will still work, since it is completely within the 1.0 spec
[09:11:12 CDT(-0500)] <EricDalquist> its pretty easy, let me find an exampl
[09:11:22 CDT(-0500)] <Arvids> that whould help me a lot
[09:11:49 CDT(-0500)] <EricDalquist> the calendar portlet does it: https://source.jasig.org/portlets/CalendarPortlet/trunk
[09:12:14 CDT(-0500)] <EricDalquist> finding specific files ....
[09:13:23 CDT(-0500)] <EricDalquist> so in this JSP: https://source.jasig.org/portlets/CalendarPortlet/trunk/src/main/webapp/WEB-INF/jsp/calendarWideView.jsp
[09:13:43 CDT(-0500)] <EricDalquist> look for the <portlet:resourceURL/> tag
[09:13:50 CDT(-0500)] <EricDalquist> that generates a URL that will result in a resource request
[09:14:10 CDT(-0500)] <EricDalquist> then here is the spring 3.0 annotated controller that handles the resource request: https://source.jasig.org/portlets/CalendarPortlet/trunk/src/main/java/org/jasig/portlet/calendar/mvc/controller/AjaxCalendarController.java
[09:14:25 CDT(-0500)] <EricDalquist> are you familiar at all with the resource request features of portlet 2.0?
[09:14:51 CDT(-0500)] <Arvids> just heard about them
[09:15:18 CDT(-0500)] <Arvids> Looks like i'll have another reading material
[09:15:19 CDT(-0500)] <EricDalquist> it essentially lets you make requests to a portlet where the portlet has complete control over the response
[09:15:41 CDT(-0500)] <Arvids> yes, that's what i was assuming
[09:15:42 CDT(-0500)] <EricDalquist> there is no portal rendered content, so you can return JSON, binary image date, etc...
[09:16:02 CDT(-0500)] <Arvids> ahh... well.. that's the key here
[09:16:06 CDT(-0500)] <EricDalquist> the big advantage of resource urls over that AJAX in a portlet approach from portlet 1.0 is fewer requests
[09:16:35 CDT(-0500)] <Arvids> how does that come?
[09:16:40 CDT(-0500)] <EricDalquist> the ajax in a 1.0 portlet approach results in a POST then 302 redirect to a servlet
[09:17:19 CDT(-0500)] <EricDalquist> the POST is done to an action URL so that the portlet can handle the request, it sets up the data to return and sticks it in the session then redirects to a servlet
[09:17:28 CDT(-0500)] <EricDalquist> and the servlet actually writes the data out from the session
[09:17:40 CDT(-0500)] <Arvids> yes, i'm familiar with that workflow
[09:17:42 CDT(-0500)] <EricDalquist> where as the resource approach is just a single request
[09:18:03 CDT(-0500)] <EricDalquist> the portal passes it on to the portlet for handling and simply returns whatever the portlet returns
[09:18:13 CDT(-0500)] <Arvids> ok