Thierry Delprat tiry

Introduction

This simple exercise has as an objective to make the candidate familiar with Nuxeo Software, and will serve as base of discussion for the interviews.

The candidate is free to chose the methodology that he feels more confortable.

The candidate can express freely his own ideas and the best of his own devops craft skills.

Nuxeo Event System is part of nuxeo-core and provide :

a way to fire events
- events are associated with context (user, document)
- the repository does fire event for pretty much everything it does
- all services (custom or not) can choose to fire any type of event associated with any type of context
a way to listen to events

Concept: Browse Nuxeo assets via Tag and 3D rendering

What it could look like: 3D VR Content View

nuxeo-importer-core contains several sample codes that can be adapted to run imports leveraging :

Why does most of the traffic go to the primary MongoDB node?

In a MongoDB cluster:

all write traffic has to go to the primary node
- it is responsible for dispatching to the other nodes
by default, most of the read traffic also goes to the primary node
- this is the default and safest option

You can alter that behavior by using Read and Write concerns

	<?xml version="1.0"?>
	<component name="RequestControllerService.defaultContrib.override">
	<require>org.nuxeo.ecm.platform.web.common.requestcontroller.service.RequestControllerService.defaultContrib</require>

	<!-- disable changes introduced by NXP-18651 -->
	<extension target="org.nuxeo.ecm.platform.web.common.requestcontroller.service.RequestControllerService"
	point="responseHeaders">
	<header name="Cache-Control" enabled="false">no-cache</header>
	<header name="Pragma" enabled="false">no-cache</header>
	</extension>