bithavoc

/*
Asymmetric Encryption Sample in Node.js: Encrypt and Decrypt using Password as a key(SECRET_KEY)
Algorithm: des-ede3-cbc (Three key Triple-DES EDE in CBC mode)
johan@firebase.co
@thepumpkin
*/

var assert = require('assert')
var crypto = require('crypto')
var Buffer = require('buffer').Buffer

zhaoyou

/*
		12306 Auto Query => A javascript snippet to help you book tickets online.
		Copyright (C) 2011-2012 Jingqin Lynn
		
		Includes jQuery
		Copyright 2011, John Resig
		Dual licensed under the MIT or GPL Version 2 licenses.
		http://jquery.org/license

		Includes Sizzle.js

dealforest

package net.dealforest.sample.crypt;

import javax.crypto.BadPaddingException;
import javax.crypto.Cipher;
import javax.crypto.IllegalBlockSizeException;
import javax.crypto.NoSuchPaddingException;
import javax.crypto.spec.IvParameterSpec;
import javax.crypto.spec.SecretKeySpec;

import java.security.InvalidKeyException;

bricef

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

/*
 * MCrypt API available online:
 * http://linux.die.net/man/3/mcrypt
 */
#include <mcrypt.h>

possibilities

From Meteor's documentation:

In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.

This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.

Basic async

Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:

JagoWang

TRANSACTION（事务隔离级别）
1. ISOLATION_DEFAULT：这是一个PlatfromTransactionManager默认的隔离级别，使用数据库默认的事务隔离级别。
每种数据库的默认隔离级别是不同的，例如SQL Server、Oracle默认Read Commited，MySQL默认Repeatable Read。
另外四个与JDBC的隔离级别相对应，不同的隔离级别采用不同的锁类型来实现，在四种隔离级别中，Serializable的
隔离级别最高，Read Uncommited的隔离级别最低。

2. ISOLATION_READ_UNCOMMITTED：读未提交数据，这是事务最低的隔离级别，在并发的事务中，它充许一个事务可以
读到另一个事务未提交的更新数据。（会出现脏读，不可重复读和幻读）

3. ISOLATION_READ_COMMITTED：读已提交数据，保证在并发的事务中，一个事务修改的数据提交后才能被另外一个事

kenyee

Make a subdirectory named packages/mynpms in your project.
Add a package.js that looks something like this:

    Package.describe({
      summary: "Custom app NPM dependencies"
    });
    
    Npm.depends({
     nconf: '0.6.7',
     feedparser: '0.16.1'

gabrielhpugliese

Router.map(function () {
    this.route('index', {
        controller: 'BasicController',
        layoutTemplate: 'indexLayout',
        path: '/',
        waitOn: function () {
            return Meteor.subscribe('Channels');
        }
    });

markgoodyear

/*!
 * gulp
 * $ npm install gulp-ruby-sass gulp-autoprefixer gulp-cssnano gulp-jshint gulp-concat gulp-uglify gulp-imagemin gulp-notify gulp-rename gulp-livereload gulp-cache del --save-dev
 */

// Load plugins
var gulp = require('gulp'),
    sass = require('gulp-ruby-sass'),
    autoprefixer = require('gulp-autoprefixer'),
    cssnano = require('gulp-cssnano'),

joyrexus

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

---

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing