Skip to content

Commit c01c02a

Browse files
authored
Update README.md
1 parent e22c439 commit c01c02a

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ A Go like concurrent system + networking/http libraries for Swift that works on
33

44
<img src="https://camo.githubusercontent.com/93de6573350b91e48ab570a4fe710e4e8baa38b8/687474703a2f2f696d672e736869656c64732e696f2f62616467652f73776966742d332e302d627269676874677265656e2e737667"> [<img src="https://travis-ci.org/noppoMan/Prorsum.svg?branch=master">](https://travis-ci.org/noppoMan/Prorsum)
55
### Why Prorsum?
6-
The reason why I started this project is because I felt it was very difficult to handle asynchronous io with Swift in the project called Slimane which I had previously made. In the Asynchronous paradigm in Swift, We need to often use the capture list well for closures and sometimes retain the object(Connection etc..) to avoid to release by ARC.
7-
Then I thought Go's concurrent/parallel and synchronous mecanism is suitable model for the present stage of Swift(If you want to write Server on the MultiCore Machine). Because we can easy to make async operations wituhout callback chains, can use full cores with simple syntax and easy to share the memory via Channel between a Thread and a Thread.
6+
The reason why I started this project is because I felt it was very difficult to handle asynchronous io with Swift in the project called [Slimane](https://github.com/noppoMan/Slimane) which I had previously made. In the Asynchronous paradigm in Swift, We need to often use the capture list well for closures and sometimes retain the object(Connection etc..) to avoid to release by ARC.
7+
Then I thought Go's concurrent/parallel and synchronous mecanism is suitable model for the present stage of Swift(If you want to write Server on the MultiCore Machine). Because we can easy to make async operations wituhout callback chains, can use Full Cores with the simple syntax and easy to share the memory via Channel between a Thread and a Thread.
88

9-
**(Prorsum is not Goroutine. Context Switch is done on the OS side, Prorsum doesn't have Corotuine. It just has thread safe shared memory mechanism(It works on the GCD) that is heavily inspired by Go.)**
9+
**(Prorsum is not Goroutine. It doesn't have Corotuines and Context Switch is done on the OS side. It just has thread safe shared memory mechanism(It works on the GCD) that is heavily inspired by Go.)**
1010

1111
### VS C10K Problem
1212
Prorsum's HTTP Server architecure is Event Driven master + Multithreading Request Handler.

0 commit comments

Comments
 (0)