type Tree =…

type Tree =
| Node of  Tree * Tree
| Leaf

it takes some time to get used to – but F# syntax is just beautiful…

#FSharp wishlist…

Simple Continiuos Integration with FAKE and windows scheduler #fsharp

Below are the details about a very simple CI setup,  the one that simply checks GitHub for changes to ‘master’ and if

there were any, runs FAKE build script.

First FAKE script:
//

The only part that should be interesting (the rest is standard FAKE) is conditional dependency for ‘Default’ task.

It depends on returned value from a custom FAKE task that checks if there are changes on GitHub.

Here is the custom task:

That is all – “simple” is the keyword  :) – here is the screenshot of it running:

Capture

Till next time…

programming languages syntax differences – (1)

  • coffeescript list = [1, 2, 3, 4]

  • c#                   var list = new List<int>() {1, 2, 3, 4);

  • boo:               list = [1, 2, 3, 4]

  • roy:                let list = (1, 2, 3, 4)

  • F#                   let list = [1; 2; 3; 4]  //semicolons?

  • nemerle:      def numbers = [1, 2, 3];

  • scala:             val list = List(1, 2, 3) 

Closures

Rolland V-Drums +  Zoom R16 Multitrack SD Recorder + Ibanez SR500 Electric Bass + Caustic Android Synth =

Equinox

Rolland V-Drums +  Zoom R16 Multitrack SD Recorder + Ibanez SR500 Electric Bass + Caustic Android Synth =

Heavy04

Rolland V-Drums +  Zoom R16 Multitrack SD Recorder + Ibanez SR500 Electric Bass + Caustic Android Synth =

My presentation from AsburyAgile 2012

A new Internet-Draft for “RESTful Authentication Pattern”

See on Scoop.itnodeJS and Web APIs

This document proposes a “RESTful” pattern of authentication for HTTP/1.0, 1.1, and 2.0. The existing 401 status code and WWW-Authenticate header are used to indicate that authentication is required and for negotiation purposes. The client POSTs an initial authentication message to an indicated login URI, and reply messages are returned as new representations of a session resource named by a session URI.

 

This approach has a number of benefits: it can be implemented with or without help from the HTTP stack, it can be universally implemented on the server side using the Common Information Gateway (CGI) and FastCGI, it results in a session Uniform Resource Identifier (URI) that can be DELETEd to logout, it is completely orthogonal to any HTTP “routers” and proxies, and it naturally (i.e., without changing HTTP) handles multi-legged authentication mechanisms.

 

Among other features supported are: channel binding, an optional round trip optimization for challenge/response mechanisms, somecryptographic protection options for clients that don’t use Transport Layer Security (TLS), stronger authentication of servers/services to users (where authentication mechanisms provide that) and more.

See on tools.ietf.org

Tutorial – anic – Faster than C, Safer than Java, Simpler than *sh!

See on Scoop.itFunctional programming

See on code.google.com

Follow

Get every new post delivered to your Inbox.

Join 266 other followers