[Building Sakai] courier in Sakai 2.9

[David Haines]

We'll give it a try ASAP.

Thanks - Dave

On Wed, Jan 23, 2013 at 3:55 PM, Jim Eng <jimeng at umich.edu> wrote:

> Dave,
>
> Just noticed that when Chuck committed the first changes to presence under
> SAK-19129, there's a note in the commit message saying this:
>
> If you put this property in:
>
> display.users.present.iframe=true
>
> Sakai will go back to its old behavior.
>
>
> I think you'd prefer having the presence changes but with courier
> available for Global Alerts, so this may not solve the problem, but it
> might be worthwhile to test that.  It's possible it will give you what you
> want without code changes.
>
> Jim
>
>
> On Jan 23, 2013, at 11:22 AM, Jim Eng wrote:
>
> Dave,
>
> Based on Matthew's suggestion, it might be a good idea for the GAM method
> in portalscripts to make an AJAX request to CourierService (for now).  That
> would seem like the smallest change you could make to get Global Alerts
> working again.  This would also have the advantage of allowing GAM to be
> enabled in MyWorkspace as well as course and project sites.
>
> It appears that the possible memory leak in Courier Service had relatively
> small impact and was never implicated in any problems experienced at
> Michigan, as far as I can tell.  So it seems like it might be OK to
> continue using CourierService for Global Alerts until an alternative is
> implemented and verified.
>
> Jim
>
>
> On Jan 23, 2013, at 11:12 AM, Jim Eng wrote:
>
> It appears that someone found a possible memory leak in CourierService and
> the decision was made to deprecate CourierService rather than fixing the
> possible memory leak.
>
>
> On Jan 23, 2013, at 11:07 AM, Matthew Jones wrote:
>
> Agreed, the way presence was changed was to use jQuery to poll by itself
> rather than rely on this service (changed in SAK-19129 - revision 82226
> specifically). You could convert GAM to poll somewhere to see if there were
> updates rather than using courier. You don't even need to poll against the
> same Sakai server.
>
> I don't remember how GAM worked, but it possibly needed some changes in
> the portal to pick up the updates. You might be able (as a temporary
> workaround) turn the old presence updates on with
> display.users.present.iframe=true
>
> But that would be less than super for performance! (And might not even be
> in the neoskin?)
>
> Recent releases of Tomcat 7 support web sockets, so this is seems like the
> ideal for those on 2.9+ in these situations, and would probably give you
> much better performance than a polling solution would, especially if you
> had a lot of things polling.
>
>
>
> On Wed, Jan 23, 2013 at 10:28 AM, Jim Eng <jimeng at umich.edu> wrote:
>
>> Dave,
>>
>> The Courier Service was deprecated back in April.  It looks like you are
>> aware of these tickets, but I'll mention them here:
>>
>>
>>    - https://jira.sakaiproject.org/browse/SAK-22053
>>    - https://jira.sakaiproject.org/browse/GAM-15
>>
>>
>> Comments in the code say there are better ways to push messages to the
>> client, but they do not say what the powers-that-be consider a better
>> approach at this point.
>>
>> As I understand it, you are looking for info about how to enable courier
>> deliveries in 2.9 and you will be looking for a better solution for 2.10.
>>
>> Jim
>>
>>
>>
>>
>> On Jan 23, 2013, at 9:03 AM, David Haines wrote:
>>
>> At Michigan we're running a contrib tool that relies on courier.  With
>> our upgrade to 2.9 the tool isn't working for us as courier no long runs
>> regularly in 2.9.  Is there a simple way to just turn the courier back on?
>>  In the long run we'll see if find an efficient way to avoid the courier
>> overhead but in the immediate term we need to get this working. While chat
>> in 2.9 uses the courier and keeps it running while the chat is open we
>> can't rely on a single tool to switch the courier on and off.  The tool in
>> question is Global Alerts which needs to be able to send it's broadcast
>> messages to users regardless of the specific tool or site they are using.
>>
>> Any ideas are welcome.
>>
>> Thanks - Dave
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130123/4e71905c/attachment.html