Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lemonldap-ng lemonldap-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 329
    • Issues 329
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #525

Closed
Open
Created Sep 06, 2012 by FX Deltombe@fxdeltombeGuest

Better manage notifications to display

LL::NG portal loads notifications to display on a strange way :

  • it loads all notifications concerning the user or all user (regardless if they are done),
  • then it generates html for all these notifications (which is quite a heavy job)
  • then, for each notification, it checks if it must be displayed or not (because already done, or because condition does not match)
  • and it loads all notifications into session data, regardless if they are displayed.

It would be much more thrifty

  • to generate html only for notifications which are displayed
  • not to store any notification into session data (it doesn't seem to be used anywhere)

Besides, it would save memory to share XSLT parser object between apache threads, instead of recreating each time a use is authenticated.

Assignee
Assign to
Time tracking