luo980/uvw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated readme and contributors list

Browse Source
This commit is contained in:
Michele Caini 2017-02-24 10:09:57 +01:00
parent 44e46490da
commit f1dba70239
2 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
AUTHORS
View File

@ -1 +1,14 @@
Michele Caini <michele dot caini at gmail dot com> # Author
Michele Caini aka skypjack
# Contributors
Federico Bertolucci aka lessness
Luca Martini aka lordlukas
Elia Mazzuoli aka Zikoel
Francesco De Felice aka fradefe
Tushar Maheshwari aka tusharpm
Paolo Monteverde aka morbo84
Jan Vcelak aka fcelda
Raoul Hecky aka raoul

17
README.md
View File

@ -121,13 +121,13 @@ The following sections will explain in short what it means to initialize and ter
Initialization is usually performed under the hood and can be even passed over, as far as handles are created using the `Loop::resource` member function.<br/> Initialization is usually performed under the hood and can be even passed over, as far as handles are created using the `Loop::resource` member function.<br/>
On the other side, handles keep themselves alive until one explicitly closes them. Because of that, memory usage will grow up if users simply forget about a handle.<br/> On the other side, handles keep themselves alive until one explicitly closes them. Because of that, memory usage will grow up if users simply forget about a handle.<br/>
Therefore the rule quickly becomes *always close your handles*. It's simple as calling the `close` member function on them. Therefore the rule quickly becomes *always close your handles*. It's as simple as calling the `close` member function on them.
#### Requests #### Requests
Usually initializing a request object is not required. Anyway, the recommended way to create a request is still through the `Loop::resource` member function.<br/> Usually initializing a request object is not required. Anyway, the recommended way to create a request is still through the `Loop::resource` member function.<br/>
Requests will keep themselves alive as long as they are bound to unfinished underlying activities. This means that users have not to discard explicitly a request.<br/> Requests will keep themselves alive as long as they are bound to unfinished underlying activities. This means that users have not to discard explicitly a request.<br/>
Therefore the rule quickly becomes *feel free to make a request and forget about it*. It's simple as calling a member function on them. Therefore the rule quickly becomes *feel free to make a request and forget about it*. It's as simple as calling a member function on them.
#### The Loop and the Resource #### The Loop and the Resource
@ -250,17 +250,8 @@ Then, to build the tests:
# Contributors # Contributors
Michele Caini aka [skypjack](https://github.com/skypjack)<br/> If you want to contribute, please send patches as pull requests against the branch master.<br/>
Federico Bertolucci aka [lessness](https://github.com/lessness)<br/> Check the [contributors list](https://github.com/skypjack/uvw/blob/master/AUTHORS) to see who has partecipated so far.
Luca Martini aka [lordlukas](https://github.com/lucamartini)<br/>
Elia Mazzuoli aka [Zikoel](https://github.com/Zikoel)<br/>
Francesco De Felice aka [fradefe](https://github.com/fradefe)<br/>
Tushar Maheshwari aka [tusharpm](https://github.com/tusharpm)<br/>
Paolo Monteverde aka [morbo84](https://github.com/morbo84)<br/>
Jan Vcelak aka [fcelda](https://github.com/fcelda)<br/>
Raoul Hecky aka raoul [raoulh](https://github.com/raoulh)
If you want to contribute, please send patches as pull requests against the branch master.
# License # License