Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Plugins should follow the release deployment cycle similar to editor's. 


Pros:          

  1. Cache issue will resolve
  2. Intermediate fix and publish will not be available


Cons:

  1. User will able to use only certain few plugins based on the configuration.

    

  1.  Sunbird deployment is required 
  2. Dynamic plugins loading features will not be available. Due to editor is bundled with specific X amount of plugins




Solution 2 - Plugin version bump-up for the contributed plugins

Present:



Proposal:

Image RemovedImage Added

As soon as the plugin fix is done before plugin get publish the developer must update the version of the plugin and , sunbird-player config update update as well to avoid the cacheand plugin search index update.

The search API should return the latest version of the plugin.


Pros:

  1. Due to version maintains, Plugin cache will resolve.
  2. Avoids the multiple portal deployment.

...

  1. Maintenance - As soon as version update, Admin as to update the sunbird player config through API .
  2. Content Update

...

  1. Upgrade is required 



Solution 3 - Dynamic updating of param tag(publish time) to plugins network request call 


API:

Code Block
API Name: '/search'

request:{
identifier”: [“plugin1”, “plugin2"]
}


As soon as plugin fix is done,Sunbird as to make an api to get the plugins metadata and pass lastUpdateOn time as config to editor's, The plugins framework should append the lastUpdatedOn field to plugins network request calls

Pros:

  1. Cache will resolve
  2. No need to portal or editor deployment
  3. No need to version update


Cons:

  1. To get last updateOn filed sunbird as to make an API call.


Metadata


Code Block
 {
  lastUpdatedOn(ms)

}


 While loading respective plugin the plugin framework should append the last updated on time to network request call by reading from metadata


Pros:

  1. No need to multiple deployment
  2. Plugins cache will resolve


Cons:

  1. Plugin framework need to update.




Conclusion:


Cache problem can not be resolved by using param tags. So each plugins as to follow the deployment process and developer need to bump up the plugin version, If any incompatibility issue. Along with user may required to upgrade the content as well.

We need further design discussion for the plugin version bump-up and content upgrade.


Kartheek Palla Vinu Kumar Venkateshwaran Selvaraj