Skip to content

Commit

Permalink
added alias to inter file links
Browse files Browse the repository at this point in the history
  • Loading branch information
jecisc committed May 22, 2015
1 parent fe52e02 commit 1fa9011
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions Fuel/Fuel.pillar
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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'.
Expand Down
2 changes: 1 addition & 1 deletion STON/STON.pillar
Original file line number Diff line number Diff line change
Expand Up @@ -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.

[[[
Expand Down

0 comments on commit 1fa9011

Please sign in to comment.