#Making components with svg When you need to put svg in templates there are some caveates. Look at this blog
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
typedef unsigned char uint8; | |
typedef unsigned int uint32; | |
typedef int int32; | |
typedef unsigned long long uint64; | |
int32 | |
add(uint32 *NumbersToSum, int32 Count) | |
{ | |
int32 Result = 0; | |
for (int32 i = 0; i < Count; i += 4) |
#What are actors
Actors are classes that process messages. Akka provides Actor
, that can be subclassed to create actors. All Actor
subclasses
must define a partial function named receive
(defined using the case construct).
Actor objects are containers for State, Behavior, MailBox, Child Actors and Supervisor Strategy. All actors must minimize unnecessary interaction via locks or shared mutable states.
##Actor reference An actor object is always to be referenced using an Actor Reference object. These references can be passed around with impunity.
REST is a specification/constraint/guideline for web applications. An application that follows these guidelines is called restful. The guidelines are on wikipedia. In short, they are:
- Separation of concerns: Clients handle the UI and user state. Servers store and manage data.
- Stateless: Every request from client will have all information relating to user state. The server will not store any information relating to user state.
- Cachable: The responses from REST server are cacheble by the browser. If you don't clear cache stale responses will be used.
- Layered: The client cannot tell if it is connected to end server or intermediary.
- Code on demand: The server can send applets or client side scripts.
- Uniform interface: This one has subcategories and I don't understand what they mean.