raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

Update docs theme

Browse source
This commit is contained in:
Peter Vlugter 2012-03-06 13:20:00 +13:00
parent f51afb9b47
commit d7fe025fa2
75 changed files with 1795 additions and 638 deletions
Download patch file Download diff file Expand all files Collapse all files

5
akka-docs/scala/actors.rst
View file

@ -6,11 +6,6 @@
################
.. sidebar:: Contents
.. contents:: :local:
The `Actor Model`_ provides a higher level of abstraction for writing concurrent
and distributed systems. It alleviates the developer from having to deal with
explicit locking and thread management, making it easier to write correct

4
akka-docs/scala/agents.rst
View file

@ -4,10 +4,6 @@
Agents (Scala)
################
.. sidebar:: Contents
.. contents:: :local:
Agents in Akka are inspired by `agents in Clojure`_.
.. _agents in Clojure: http://clojure.org/agents

4
akka-docs/scala/dataflow.rst
View file

@ -1,10 +1,6 @@
Dataflow Concurrency (Scala)
============================
.. sidebar:: Contents
.. contents:: :local:
Description
-----------

4
akka-docs/scala/dispatchers.rst
View file

@ -3,10 +3,6 @@
Dispatchers (Scala)
===================
.. sidebar:: Contents
.. contents:: :local:
An Akka ``MessageDispatcher`` is what makes Akka Actors "tick", it is the engine of the machine so to speak.
All ``MessageDispatcher`` implementations are also an ``ExecutionContext``, which means that they can be used
to execute arbitrary code, for instance :ref:`futures-scala`.

3
akka-docs/scala/event-bus.rst
View file

@ -4,9 +4,6 @@
Event Bus (Scala)
#################
.. sidebar:: Contents
.. contents:: :local:
Originally conceived as a way to send messages to groups of actors, the
:class:`EventBus` has been generalized into a set of composable traits

4
akka-docs/scala/extending-akka.rst
View file

@ -5,10 +5,6 @@
#########################
.. sidebar:: Contents
.. contents:: :local:
If you want to add features to Akka, there is a very elegant, but powerful mechanism for doing so.
It's called Akka Extensions and is comprised of 2 basic components: an ``Extension`` and an ``ExtensionId``.

4
akka-docs/scala/fault-tolerance.rst
View file

@ -3,10 +3,6 @@
Fault Tolerance (Scala)
=======================
.. sidebar:: Contents
.. contents:: :local:
As explained in :ref:`actor-systems` each actor is the supervisor of its
children, and as such each actor defines fault handling supervisor strategy.
This strategy cannot be changed afterwards as it is an integral part of the

3
akka-docs/scala/fsm.rst
View file

@ -4,9 +4,6 @@
FSM
###
.. sidebar:: Contents
.. contents:: :local:
Overview
========

3
akka-docs/scala/futures.rst
View file

@ -3,9 +3,6 @@
Futures (Scala)
===============
.. sidebar:: Contents
.. contents:: :local:
Introduction
------------

3
akka-docs/scala/io.rst
View file

@ -3,9 +3,6 @@
IO (Scala)
==========
.. sidebar:: Contents
.. contents:: :local:
Introduction
------------

3
akka-docs/scala/logging.rst
View file

@ -4,9 +4,6 @@
Logging (Scala)
#################
.. sidebar:: Contents
.. contents:: :local:
How to Log
==========

4
akka-docs/scala/remoting.rst
View file

@ -5,10 +5,6 @@
#################
.. sidebar:: Contents
.. contents:: :local:
For an introduction of remoting capabilities of Akka please see :ref:`remoting`.
Preparing your ActorSystem for Remoting

4
akka-docs/scala/routing.rst
View file

@ -4,10 +4,6 @@
Routing (Scala)
===============
.. sidebar:: Contents
.. contents:: :local:
A Router is an actor that routes incoming messages to outbound actors.
The router routes the messages sent to it to its underlying actors called 'routees'.

4
akka-docs/scala/serialization.rst
View file

@ -5,10 +5,6 @@
Serialization (Scala)
######################
.. sidebar:: Contents
.. contents:: :local:
Akka has a built-in Extension for serialization,
and it is both possible to use the built-in serializers and to write your own.

4
akka-docs/scala/testing.rst
View file

@ -8,10 +8,6 @@ Testing Actor Systems (Scala)
testkit-example
.. sidebar:: Contents
.. contents:: :local:
As with any piece of software, automated tests are a very important part of the
development cycle. The actor model presents a different view on how units of
code are delimited and how they interact, which has an influence on how to

4
akka-docs/scala/transactors.rst
View file

@ -4,10 +4,6 @@
Transactors (Scala)
#####################
.. sidebar:: Contents
.. contents:: :local:
Why Transactors?
================

4
akka-docs/scala/typed-actors.rst
View file

@ -1,10 +1,6 @@
Typed Actors (Scala)
====================
.. sidebar:: Contents
.. contents:: :local:
Akka Typed Actors is an implementation of the `Active Objects <http://en.wikipedia.org/wiki/Active_object>`_ pattern.
Essentially turning method invocations into asynchronous dispatch instead of synchronous that has been the default way since Smalltalk came out.

4
akka-docs/scala/zeromq.rst
View file

@ -6,10 +6,6 @@
################
.. sidebar:: Contents
.. contents:: :local:
Akka provides a ZeroMQ module which abstracts a ZeroMQ connection and therefore allows interaction between Akka actors to take place over ZeroMQ connections. The messages can be of a proprietary format or they can be defined using Protobuf. The socket actor is fault-tolerant by default and when you use the newSocket method to create new sockets it will properly reinitialize the socket.
ZeroMQ is very opinionated when it comes to multi-threading so configuration option `akka.zeromq.socket-dispatcher` always needs to be configured to a PinnedDispatcher, because the actual ZeroMQ socket can only be accessed by the thread that created it.