MaximeFrancoeur

'use strict';
 
/**
 * router-state-eq Directive
 *
 * What does this directive do?
 * Analyses the current $state and allows us to apply a css class depending on true/false
 *
 * How to use it?
 * Apply the router-state-eq="" attribute to the DOM element you want to style

MaximeFrancoeur

INSERT INTO country (id, iso, name_const, name, iso3, numcode, phonecode) VALUES
(1, 'AF', 'AFGHANISTAN', 'Afghanistan', 'AFG', 4, 93),
(2, 'AL', 'ALBANIA', 'Albania', 'ALB', 8, 355),
(3, 'DZ', 'ALGERIA', 'Algeria', 'DZA', 12, 213),
(4, 'AS', 'AMERICAN SAMOA', 'American Samoa', 'ASM', 16, 1684),
(5, 'AD', 'ANDORRA', 'Andorra', 'AND', 20, 376),
(6, 'AO', 'ANGOLA', 'Angola', 'AGO', 24, 244),
(7, 'AI', 'ANGUILLA', 'Anguilla', 'AIA', 660, 1264),
(8, 'AQ', 'ANTARCTICA', 'Antarctica', NULL, NULL, 0),

MaximeFrancoeur

var AWS   = require("aws-sdk");
var DOC   = require("dynamodb-doc");
var path  = require('path');
var util  = require('util');
var _     = require('lodash');
var async = require('async');

var internals = {};

MaximeFrancoeur

class BaseService {
    public void save(){
        validate();
    }
}

public ChildService extends BaseService{
    public void save(){
        super.save()
        load();

MaximeFrancoeur

@Mock private SmtpConnection smtpConnection;
 
private void mockSmtpConnection() {
    final ArgumentCaptor<String> recipient = ArgumentCaptor.forClass(String.class);
    final ArgumentCaptor<String> subject = ArgumentCaptor.forClass(String.class);
    final ArgumentCaptor<String> body = ArgumentCaptor.forClass(String.class);
 
    when(smtpConnection.setRecipient(recipient.capture()))
        .thenReturn(smtpConnection);
    when(smtpConnection.setSubject(subject.capture()))

MaximeFrancoeur

public class PomVersion {
    final private static Logger LOGGER = LogManager.getLogger(PomVersion.class);

    final static String VERSION = loadVersion();

    private static String loadVersion() {
        Properties properties = new Properties();
        try {
            InputStream inStream = PomVersion.class.getClassLoader().getResourceAsStream("version.properties");
            properties.load(inStream);

MaximeFrancoeur

Session Management in an Autoscaling Environment

Problem Statement

User sessions in J2EE and LAMP stacks have traditionally been handled in memory by the application server handling the user request. Because of that, load balancers have been configured to use sticky sessions. By sticky sessions we mean that once the user has visited the site, they will be assigned an app server and will return to that server for subsequent requests. The load balancers typically handle that by referencing the users session cookie.

Elastic cloud environments differ from traditional server configurations in that they have a variable number of servers based on traffic loads whereas traditional configurations had a fixed number of servers. When traffic volumes decline it is necessary to vaporize servers. In doing so, we would lose user sessions (essentially forcing a logout) unless we come up with a new strategy for session management.

A new approach

After much research, it is clear that the best

MaximeFrancoeur

import javax.crypto.Mac;
import javax.crypto.spec.SecretKeySpec;
import java.io.UnsupportedEncodingException;
import java.security.InvalidKeyException;
import java.security.NoSuchAlgorithmException;
public class HMAC {

  public static void main(String[] args) throws Exception {
    System.out.println(hmacDigest("The quick brown fox jumps over the lazy dog", "key", "HmacSHA1"));
  }

MaximeFrancoeur

find ./ -type f -exec perl -pi -e 's/\r\n|\n|\r/\n/g' {} \;

MaximeFrancoeur

import java.util.Set;
import java.util.concurrent.ConcurrentHashMap;

public class HelloCovariance {
  public static void main(String[] args) {
    ConcurrentHashMap<String, String> properties = new ConcurrentHashMap<>();
    Set<String> keySet = properties.keySet();
  }
}