-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
136 lines (83 loc) · 5.94 KB
/
atom.xml
File metadata and controls
136 lines (83 loc) · 5.94 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Messing with GT.M]]></title>
<link href="http://ozgunbas.github.com/atom.xml" rel="self"/>
<link href="http://ozgunbas.github.com/"/>
<updated>2012-08-12T18:58:27-04:00</updated>
<id>http://ozgunbas.github.com/</id>
<author>
<name><![CDATA[Erdeniz Bas]]></name>
<email><![CDATA[ozgunbas@gmail.com]]></email>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[Hello World example]]></title>
<link href="http://ozgunbas.github.com/blog/2012/08/12/hello-world-example/"/>
<updated>2012-08-12T18:44:00-04:00</updated>
<id>http://ozgunbas.github.com/blog/2012/08/12/hello-world-example</id>
<content type="html"><![CDATA[<p>In this post we will write a simple M code and understand basic syntax. Let’s start with the example code:<br /></p>
<script src="https://gist.github.com/2691329.js?file=hello">
</script>
<br />
<br />
<ul>
<li>First column in M is reserved for labels (Line 1). Labels are entry references which can be used to transfer execution. </li>
<li>Line 2 explains itself :) </li>
<li>Line 3 prints “Hello world” string to the screen and breaks the line. ‘!’ character does the line breaking part. <i>write</i> can take multiple strings separated by a comma. Notice comma is not a string concatenation operator. </li>
<li>Line 4 returns the execution to its caller. In this case <i>quit</i> is not necessary because we are already at the end of our code. However, it is a good practice to add it at the end of every section. If we decide to add more code later and forget to add <i>quit</i>. Execution will continue to the next command in order without jumping or quitting (may not be what we want).</li>
</ul>
]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Let's do it! GT.M Overview]]></title>
<link href="http://ozgunbas.github.com/blog/2012/08/12/lets-do-it-gt-dot-m-overview/"/>
<updated>2012-08-12T18:40:00-04:00</updated>
<id>http://ozgunbas.github.com/blog/2012/08/12/lets-do-it-gt-dot-m-overview</id>
<content type="html"><![CDATA[<h3>
What is it?</h3>
<p>GT.M is an open-source implementation of M (a.k.a. <a href="http://en.wikipedia.org/wiki/MUMPS" target="_blank">MUMPS</a>) language. M is a hierarchical, multi-dimensional database. Unlike SQL, data is not conceptually stored in “tables” so it gives a higher flexibility to programmers who have varying-length “rows”. Programmers have full control and higher understanding of how data is represented in the memory so they can optimize data structure for faster data access. It does not require predefined types associated with each row and column. Types are dynamically converted from one to another depending on the usage. GT.M is <a href="http://sourceforge.net/projects/fis-gtm/" target="_blank">open source</a> and free on Linux. Other platforms (AIX, Solaris, TruUnix, HP-UX) are supported, but are not free.<br /></p>
<div>
<br />
<h3>
Who uses it?</h3>
</div>
<p>GT.M is currently used by major hospitals and banks. It is capable of handling massive concurrent transactions (10K or more). For this reason, it is ideal for programmers who does not want to compromise speed, and interested in crafting systems that goes beyond “tables” and rows.<br /></p>
<br />
<h3>
Is it reliable?</h3>
<p>GT.M supports ACID (Atomic, consistent, transactions, isolated, durable) transaction processing that most of the database engines provide today. It is as easy as putting your critical updates between “TStart” and TCommit keywords :)<br /></p>
<br />
<p>Another important feature GT.M also supports is replication, which is a disaster recovery measure to support business continuity. It is achieved by having two sites where the primary site is monitored by the secondary site. The events on the primary site are replicated by the secondary site. If the primary site goes down, the secondary site automatically handles transaction in the matter of seconds. That will buy system administrators some time to fix the problem without any disruptions in service.<br /></p>
<br />
<h3>
Is it secure?</h3>
<div>
GT.M supports encryption using GPG.</div>
<br />
<h3>
Is it portable?</h3>
<p>GT.M complies MUMPS standards determined by MUMPS standards committee. This means that code developed in GT.M is expected to work on any standard MUMPS compliant implementation.<br /></p>
<br />
<h3>
How do I test it?</h3>
<p>If you want to learn how to set up your installation:<br /></p>
<ul>
<li>Take a look at <a href="http://tinco.pair.com/bhaskar/gtm/doc/books/ao/UNIX_manual/index.html" target="_blank">GT.M administrator’s manual</a> or</li>
<li>Read this sweet blog post by <a href="http://opensource.com/health/12/3/join-m-revolution%E2%80%94get-your-tools" target="_blank">Luis Ibanez</a>.</li>
</ul>
<br />
<br />
<p>In the following posts, I will give some interesting code examples with their explanations, and introduce some useful features in detail.<br /></p>
<br />
]]></content>
</entry>
<entry>
<title type="html"><![CDATA[First Post]]></title>
<link href="http://ozgunbas.github.com/blog/2012/08/12/first-post/"/>
<updated>2012-08-12T14:02:00-04:00</updated>
<id>http://ozgunbas.github.com/blog/2012/08/12/first-post</id>
<content type="html"><![CDATA[<p>Hello World! Testing, testing…</p>
<p>It’s been a long time since I haven’t made a new post to my former <a href="http://gtmprogramming.blogspot.com/">blog</a>. That’s because it is so much pain to embed code into blogspot. I hope octopress makes this easy. I’ll port my older posts from there to here, and see what I can do with my newer posts’ code examples. Stay tuned!</p>
]]></content>
</entry>
</feed>