wtrocki

subscription subscribeTasks{
    subscribeTasks{
        id
        title
        description
        version
    }
}

wtrocki

subscription SubscribeData{
    subscribeTasks{
        id
        title
        description
        version
    }
}

wtrocki

let config = {
  "version": 1,
  "namespace": "test",
  "clientId": "org.aerogear.ionic.showcase",
  "services": [
    {
      "id": "e339e761-3687-11e9-9467-0af08791569c",
      "name": "sync-app-test-org.aerogear.ionic.showcase",
      "type": "sync-app",
      "url": "https://sync-app-showcase-server-demo.comm2.skunkhenry.com/graphql",

wtrocki

// Takes string of Note + Octave
// Example:
// var frequency = getFrequency('C3');

var getFrequency = function (note) {
    var notes = ['A', 'A#', 'B', 'C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#'],
        octave,
        keyNumber;

    if (note.length === 3) {

wtrocki

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

wtrocki

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.cards.notification">

    <uses-sdk
        android:minSdkVersion="17"
        android:targetSdkVersion="17" />

    <application
        android:allowBackup="true"

wtrocki

#!/bin/sh

set -x

TAG=1.0.0-alpha

oc patch deployment webconsole -n openshift-web-console -p "{\"spec\": {\"template\": {\"spec\": {\"containers\": [{\"name\": \"webconsole\", \"image\": \"aerogear/origin-web-console:$TAG\"}]}}}}"

#oc get configmap broker-config -n ansible-service-broker -o yaml | sed -e "s/tag:.*/tag: \"$TAG\"/" | oc replace -n ansible-service-broker -f -

wtrocki

HTTP Rest API receive 'push request', this gets processed in PushNotificationSenderEndpoint.send(), which eventually calls an async EJB (NotificationRouter.submit()) which performs a grouping/mapping and fires a CDI event per Variant.

This Event is received in the MessageHolderWithVariantsProducer.queueMessageVariantForProcessing() method, which basically sticks the submitted event into a transactional JMS send, based on the variant type a different queue is selected (mainly to keep things separated). The JMS listener MessageHolderWithVariantsConsumer.onMessage() reads from these queues, and fires a different CDI event, which kicks in the TokenLoader.

The TokenLoader generally iterates over all variants (for a given type, see the grouping/mapping done in NotificationRouter), and starts to query tokens from the database, as a steam.

The tokens are in different batches, with different default sizes per Push_Network, to not overflow the push network (e.g. google (non topic case) only allows 1

wtrocki

//
//  MetricsIntegrationTest.swift
//  AeroGearSdkExampleTests

@testable import AGSCore
import Foundation
import XCTest

wtrocki

{
  "parser": "babel-eslint",
  "plugins": [
    "react",
    "react-native"
  ],
  "parserOptions": {
    "ecmaFeatures": {
        "jsx": true,
        "modules": true