Alongside Me

The pain comes in waves. Each one stronger than the ones before. I do not trust myself to be alone right now, so I let my tears run free in public when random unrelated trinkets reminds me of her. So many died recently so little joy left in life.

• Stocked up on a lot of junk food for crunch time. #
• Cookie hashing, password salt and hash done. Everything's secure #
• Oh yeah and figure out how to set the image path. #
• There's so much to do. Google+ integration. Hashing, encryption. #
• Login/logout, session cookies implemented. Proceed to hashing and salting passwords. #

• Observed a young couple signing the house at starbucks. Heard them say the same thing I did to the agent. I feel sad for them. #
• Allright socialist government, I've banked enough money. Hit me with your property taxes. #
• #fail Starbucks ash port not opened. Cloud server setup to receive only ssh #
• Can't figure out why database is not synching. No problem. Goto Starbucks. #
• Ok EC2 test web server up and running. Too tired. #
• Finally found a caffein free replacement for tea: Green Rooibos #
• EC2 up SSH established. #
• @Azhwi canned salmon is too expensive of an ingredient to go with cheapo toast IMHO #
• ~toerun 6.5km time 00:41:03 heartrate 150bpm #
• Ahh the simple joy of Tuna sandwich with chopped green onion. #
• Amazon EC2 instance initialized. Linux environment setup complete. Testing functionalities… #
• Part of the problem of being old is that we got used to communication as a means to move an agenda and don't enjoy it for just it. #
• Allright, blog functionality is a go: http://t.co/k5SwFkD9 Next, deploy on AWS #
• I've finally broken the 30 minute barrier on 5km runs #
• ~toerun 5km heartrate 186bpm time 00:29:25 #
• Created my own blog from scratch after 6 hours. But there are some bugs I did not see on my PC… quirks of cloud PC: http://t.co/Rkrd6dTk #
• Week 3 and we are already building our own blog framework. Getting interesting. #
• Couldn't get AWS sqs working. Too tired. #
• AWS s3 Linux working. #
• GAE Linux environment setup complete. Test deploy successful. #
• Setting up dev environment for AWS and GAE in Linux. #

Readers beware, beyond this lies codes only

Read the rest of this entry »

Inventor of actor model: Carl Hewitt

-Actor is a primitive unit that embodies all fundamental elements of computation needs.

• Processing: Get something done
• Storage: Be able to remember things
• Communication:

-You cannot have just one actors. A system of actors that can communicate with each other make up actors.

-Fundamental properties of actor

• Everything is an actor
• Then you are recursed to no end
• But the actor end in axioms
• What can an actor do:
  • Create another actor,
  • Send message to other actors
  • Designate how its going to handle the next message
• Process one message at a time:
  • Implement a pipeline to take message queue
  • If messages in pipeline are all the same, process it all at once.
• Idea of a futures contract:
  • While its processing something you can buy a future to process in it
  • If it breaks, the futures contract breaks
  • So you can send this future to yourself and you don’t get a deadlock for sending message to yourself.
  • So you can get the future immediately and pass it around and store it
• Is address equivalent to identity?
  • No because you can have one address for a bunch of actors replicated behind the scenes
  • It could be a message box that forwards to a bunch of other actors
• On Addresses
  • All you can do with an address is send a message
  • CLR enforces address integrity
  • Between the machines, you use encryption
  • Cannot take an integer and cast it to an object
  • It is too expensive on the system to maintain sequential time messaging arrival. Just like internet packets
  • Addresses are like capabilities
  • Messages are sent via best effort
  • There are no channels, if you want it, it’ll be another actor
• Messaging is indeterministic: they sort themselves out
  • Start mesage
  • Go message, stop message
  • Consider the case of sending myself a message
  • If I get a go message, I increment the counter by one and send a go message
  • Synchronization is built into the fact that one message is handled at a time. In the order they arrived. Like a checking account
  • This is where the arbitor comes in
  • If I get a stop message, then I report what the count is
• Arbitors
  • Arbitors cannot be made out of AND gates and OR gates
  • 2 inputs i1 and i2.
  • 2 outputs o1 and o2
  • Allowed to put in i1 and i2 at the same time, but only 1 can come out of outputs
  • An arbitor may take however long it needs to decide, but it must decide
  • It is used to decide which inputs came in first.
• Assignment:
  • In the checking account example: Actor returns the balance and also, the balance+ deposit
  • So the answer and the assignment as well.
• You can’t enforce consistency. There’s no way to compute truth in absolute term
• You can not get a global picture, so only a local situation.