From 1fa90111f2c203747965e91453d3bafe2bfadeb2 Mon Sep 17 00:00:00 2001 From: Cyril Ferlicot Date: Fri, 22 May 2015 17:55:55 +0200 Subject: [PATCH] added alias to inter file links --- Fuel/Fuel.pillar | 4 ++-- STON/STON.pillar | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Fuel/Fuel.pillar b/Fuel/Fuel.pillar index 9759b76..0d400cc 100644 --- a/Fuel/Fuel.pillar +++ b/Fuel/Fuel.pillar @@ -7,7 +7,7 @@ Leske. It is robust and used in many industrial cases. A fundamental reason for the creation of Fuel was speed: while there is a plethora of frameworks to serialize objects based on recursive parsing of the object graphs in textual format as XML, JSON, or STON, these -approaches are often slow. (For JSON and STON see also Chapter *../STON/STON.pillar@ch:ston*.) +approaches are often slow. (For JSON and STON see also Chapter *STON>../STON/STON.pillar@ch:ston*.) Part of the speed of Fuel comes from the idea that objects are loaded more often than stored. This makes it worth to spend more time while storing to yield faster loading. Also, its storage scheme is based on the pickle format that puts similar objects into groups for efficiency and performance. As a result, Fuel @@ -116,7 +116,7 @@ materializedString := FLMaterializer materializeFromFileNamed: 'demo.fuel'. Fuel also provides the messages ==serializeToByteArray:== and ==materializeFromByteArray:== for storing into a ==ByteArray==. This can be interesting, for example, for serializing an object graph as a -blob of data into a database when using Voyage (see Chapter *../Voyage/Voyage.pillar@ch:voyage*). +blob of data into a database when using Voyage (see Chapter *Voyage>../Voyage/Voyage.pillar@ch:voyage*). [[[language=Smalltalk anArray := FLSerializer serializeToByteArray: 'stringToSerialize'. diff --git a/STON/STON.pillar b/STON/STON.pillar index 24340bf..b123891 100644 --- a/STON/STON.pillar +++ b/STON/STON.pillar @@ -136,7 +136,7 @@ TestDomainObject { !!!! A large example: an HTTP response Here is a more complex example: a ZnResponse object. It is the result of serializing the result of the following HTTP request (using Zinc, see -Chapters *../Zinc-HTTP-Client/Zinc-HTTP-Client.pier@ch:zinc-client* and *../Zinc-HTTP-Server/Zinc-HTTP-Server.pier@ch:zinc-server*). It also shows that curly +Chapters *Zinc Client>../Zinc-HTTP-Client/Zinc-HTTP-Client.pier@ch:zinc-client* and *Zinc Server>../Zinc-HTTP-Server/Zinc-HTTP-Server.pier@ch:zinc-server*). It also shows that curly braces are for dictionaries and square brackets are for lists. [[[