blob: bc199e428edf5c2f497ae724e10553a233fc6d10 [file] [log] [blame]
Kevin Clark7618fb42008-06-18 01:02:46 +00001#!/usr/local/bin/thrift --gen cpp --gen java --gen py --php --gen rb --gen perl --erl --xsd -r
Mark Slee07a3aab2007-03-07 05:45:10 +00002#
3# Thrift Tutorial
4# Mark Slee (mcslee@facebook.com)
5#
6# This file aims to teach you how to use Thrift, in a .thrift file. Neato. The
7# first thing to notice is that .thrift files support standard shell comments.
8# This lets you make your thrift file executable and include your Thrift build
9# step on the top line. And you can place comments like this anywhere you like.
10#
11# Before running this file, you will need to have installed the thrift compiler
12# into /usr/local/bin.
13
14/**
15 * The first thing to know about are types. The available types in Thrift are:
16 *
17 * bool Boolean, one byte
18 * byte Signed byte
19 * i16 Signed 16-bit integer
20 * i32 Signed 32-bit integer
21 * i64 Signed 64-bit integer
22 * double 64-bit floating point value
23 * string String
24 * map<t1,t2> Map from one type to another
25 * list<t1> Ordered list of one type
26 * set<t1> Set of unique elements of one type
27 *
28 * Did you also notice that Thrift supports C style comments?
29 */
30
31// Just in case you were wondering... yes. We support simple C comments too.
32
33/**
34 * Thrift files can reference other Thrift files to include common struct
35 * and service definitions. These are found using the current path, or by
36 * searching relative to any paths specified with the -I compiler flag.
37 *
38 * Included objects are accessed using the name of the .thrift file as a
39 * prefix. i.e. shared.SharedObject
40 */
41include "shared.thrift"
42
43/**
44 * Thrift files can namespace, package, or prefix their output in various
45 * target languages.
46 */
David Reiss9a08dc62008-02-27 01:55:17 +000047namespace cpp tutorial
David Reiss771f8c72008-02-27 01:55:25 +000048namespace java tutorial
Mark Slee07a3aab2007-03-07 05:45:10 +000049php_namespace tutorial
David Reiss07ef3a92008-03-27 21:42:39 +000050namespace perl tutorial
David Reiss3b455012008-03-27 21:40:46 +000051namespace smalltalk.category Thrift.Tutorial
Mark Slee07a3aab2007-03-07 05:45:10 +000052
53/**
54 * Thrift lets you do typedefs to get pretty names for your types. Standard
55 * C style here.
56 */
57typedef i32 MyInteger
58
59/**
60 * Thrift also lets you define constants for use across languages. Complex
61 * types and structs are specified using JSON notation.
62 */
63const i32 INT32CONSTANT = 9853
64const map<string,string> MAPCONSTANT = {'hello':'world', 'goodnight':'moon'}
65
66/**
67 * You can define enums, which are just 32 bit integers. Values are optional
68 * and start at 1 if not supplied, C style again.
69 */
70enum Operation {
71 ADD = 1,
72 SUBTRACT = 2,
73 MULTIPLY = 3,
74 DIVIDE = 4
75}
76
77/**
78 * Structs are the basic complex data structures. They are comprised of fields
79 * which each have an integer identifier, a type, a symbolic name, and an
80 * optional default value.
David Reiss5ff21a42008-07-24 19:13:54 +000081 *
82 * Fields can be declared "optional", which ensures they will not be included
83 * in the serialized output if they aren't set. Note that this requires some
84 * manual management in some languages.
Mark Slee07a3aab2007-03-07 05:45:10 +000085 */
86struct Work {
87 1: i32 num1 = 0,
88 2: i32 num2,
David Reiss5ff21a42008-07-24 19:13:54 +000089 3: Operation op,
90 4: optional string comment,
Mark Slee07a3aab2007-03-07 05:45:10 +000091}
92
93/**
94 * Structs can also be exceptions, if they are nasty.
95 */
96exception InvalidOperation {
97 1: i32 what,
98 2: string why
99}
100
101/**
102 * Ahh, now onto the cool part, defining a service. Services just need a name
103 * and can optionally inherit from another service using the extends keyword.
104 */
105service Calculator extends shared.SharedService {
David Reiss0c90f6f2008-02-06 22:18:40 +0000106
Mark Slee07a3aab2007-03-07 05:45:10 +0000107 /**
108 * A method definition looks like C code. It has a return type, arguments,
109 * and optionally a list of exceptions that it may throw. Note that argument
110 * lists and exception lists are specified using the exact same syntax as
111 * field lists in struct or exception definitions.
112 */
113
114 void ping(),
115
116 i32 add(1:i32 num1, 2:i32 num2),
117
118 i32 calculate(1:i32 logid, 2:Work w) throws (1:InvalidOperation ouch),
119
120 /**
121 * This method has an async modifier. That means the client only makes
122 * a request and does not listen for any response at all. Async methods
123 * must be void.
124 */
125 async void zip()
126
127}
128
129/**
130 * That just about covers the basics. Take a look in the test/ folder for more
131 * detailed examples. After you run this file, your generated code shows up
132 * in folders with names gen-<language>. The generated code isn't too scary
133 * to look at. It even has pretty indentation.
134 */