From 636c51a6f371dc7efd32d183ef6a88c5b93dd223 Mon Sep 17 00:00:00 2001 From: anhefti Date: Tue, 11 May 2021 21:58:42 +0200 Subject: [PATCH] docu --- .../servicelayer/lms/impl/moodle/MoodleCourseAccess.java | 5 +++-- .../servicelayer/lms/impl/moodle/MoodleLmsAPITemplate.java | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleCourseAccess.java b/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleCourseAccess.java index 77989adf..6255c5d9 100644 --- a/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleCourseAccess.java +++ b/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleCourseAccess.java @@ -58,8 +58,9 @@ import ch.ethz.seb.sebserver.webservice.servicelayer.lms.impl.moodle.MoodleRestT * in an easy and proper way. Therefore we have to fetch all course and quiz data from Moodle before * filtering and paging can be applied. Since there are possibly thousands of active courses and quizzes * this moodle course access implements an synchronous fetch as well as an asynchronous fetch strategy. - * The asynchronous fetch strategy is started within a background task and fill up a shared cache. - * A request will start the background task if needed and return immediately to do not block the request. + * The asynchronous fetch strategy is started within a background task that batches the course and quiz + * requests to Moodle and fill up a shared cache. A SEB Server LMS API request will start the + * background task if needed and return immediately to do not block the request. * The planed Moodle integration on moodle side also defines an improved course access API. This will * possibly make this synchronous fetch strategy obsolete in the future. */ public class MoodleCourseAccess extends CourseAccess { diff --git a/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleLmsAPITemplate.java b/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleLmsAPITemplate.java index f9784a4f..3cdb489f 100644 --- a/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleLmsAPITemplate.java +++ b/src/main/java/ch/ethz/seb/sebserver/webservice/servicelayer/lms/impl/moodle/MoodleLmsAPITemplate.java @@ -42,8 +42,9 @@ import ch.ethz.seb.sebserver.webservice.servicelayer.lms.impl.NoSEBRestrictionEx * in an easy and proper way. Therefore we have to fetch all course and quiz data from Moodle before * filtering and paging can be applied. Since there are possibly thousands of active courses and quizzes * this moodle course access implements an synchronous fetch as well as an asynchronous fetch strategy. - * The asynchronous fetch strategy is started within a background task and fill up a shared cache. - * A request will start the background task if needed and return immediately to do not block the request. + * The asynchronous fetch strategy is started within a background task that batches the course and quiz + * requests to Moodle and fill up a shared cache. A SEB Server LMS API request will start the + * background task if needed and return immediately to do not block the request. * The planed Moodle integration on moodle side also defines an improved course access API. This will * possibly make this synchronous fetch strategy obsolete in the future. */ public class MoodleLmsAPITemplate implements LmsAPITemplate {