simong

#!/usr/bin/python

class Node(object):
    left = None
    right = None
    value = None
  
    def __init__(self, val):
        self.value = val

simong

What I have: oae-authentication/lib/api.js: ... _$jscoverage['api.js'][138] = 0; _$jscoverage['api.js'][139] = 0; _$jscoverage['api.js'][140] = 0; ...

oae-permissions/lib/api.js:

simong

var helenus = require('helenus'),
    pool = new helenus.ConnectionPool({
        hosts      : ['localhost:9160'],
        keyspace   : 'oae',
        user       : '',
        password   : '',
        timeout    : 3000
    });

pool.on('error', function(err){

simong

OAE Loader

A list of tasks that need to happen to ensure we get consistent results out of each dataload that can be easily compared to each other.

Clean the system

We should try to bring the system into the same state for each dataload/benchmark. The simplest way is to just wipe everything and start fresh.

simong

The content module for Sakai OAE

Cassandra model

Column families

1. Content

Holds the actual metadata for a piece of content

2. LibraryByPrincipal

Three rows per principal that each holds IDs of the content items that are visible in this library.

simong

#createTenant.sh
#!/bin/bash

if [ "$1" = "--usage" ] ; then
    echo "All parameters are optional. The default options will "
    echo "create a cambridge tenant as in the example."
    echo "--------------------------------------------------------"
    echo "./createTenant.sh <alias:cam> <tenant name:Cambridge> <hostname:cam.oae.com>"
    echo "--------------------------------------------------------"
    echo "Example:"

simong

# Startup
All the storage backends register themselves.
ContentAPI.Backends.register('local', require('backends/local'))
ContentAPI.Backends.register('amazons3', require('backends/amazons3'))
...


# An upload request
1. User uploads to /api/content/create
2. Gets routed to ContentAPI.createFile

simong

Preview Processor Registration Pattern

In order to make the Preview Processing a bit more maintainable, future proof and allow for easy 3rd party integration we need some sort of pluggable system that allows us to register new processors.

Each processor should register itself with the PP api so that it can be picked up and handed content items. Whenever a content item needs preview processing, all registered processors will be checked if they can handle the file. They should each return a number of how well suited they are to deal with the piece of content. The processor that returns the highest number will be chosen to generate the preview images.

simong

Reset password pointers

General workflow

1. The user 'Alice' forgets the password of her local account
2. She clicks the 'Forgot my password'-link which takes her to /resetpassword
3. A page with a form is displayed where she can enter the username she uses to login with (we currently do not have the functionality to look up a user by email)
4. She fills in her username and submits the form
5. The backend sends an e-mail to the e-mail address that is stored with the 'Alice' account

simong

            "filter": {
                "and": [
                    {
                        "and": [
                            {
                                "term": {
                                    "_type": "resource"
                                }
                            },
                            {