Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-32035

Replace courier service in chat with some other service

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.8 [Tentative], 11.3, 12.0
    • Fix Version/s: 12.0
    • Component/s: Chat
    • Labels:

      Description

      Courier service was deprecated in SAK-22053 in 2.9 but still is used by the chat tool. This backend should be replaced by some other service, possibly jGroups which is what the portal chat uses. Using the same back-end as portal chat might also make it easier for chat tool messages to be easily accessible from the portal chat dialog so you don't have to go directly into each sites tool! (Another feature perhaps)

      Sometimes courier goes down and needs a restart to work again and it has other issue mentioned in that original ticket. I think there is the issue of having an abstraction layer instead (SAK-22359) but this feels a little less of a concern.

      It might be better to do it at a higher level like MessageService (like this ticket mentioned) but I'm not sure about the implementation details. This will likely be a FARM project.

        Gliffy Diagrams

          Attachments

          1. chat_diagram.pdf
            25 kB
          2. ui_improvement_1.jpg
            ui_improvement_1.jpg
            71 kB
          3. ui_improvement_2.jpg
            ui_improvement_2.jpg
            78 kB

            Issue Links

              Activity

                People

                • Assignee:
                  farreri Miguel Pellicer
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code