Skip to content

Commit

Permalink
Ammending the intro text
Browse files Browse the repository at this point in the history
  • Loading branch information
madflojo committed Dec 25, 2019
1 parent db0f60f commit 61fc0cf
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 4 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,9 @@
[![Go Report Card](https://goreportcard.com/badge/github.com/madflojo/tasks)](https://goreportcard.com/report/github.com/madflojo/tasks)
[![Documentation](https://godoc.org/github.com/madflojo/tasks?status.svg)](http://godoc.org/github.com/madflojo/tasks)

Package tasks is an easy to use in-process task scheduler for Go. Focused on interval based execution, Tasks provides
both recurring and one-time task scheduling.
Package tasks is an easy to use in-process scheduler for recurring tasks in Go. Tasks is focused on high frequency
tasks that run quick, and often. The goal of Tasks is to support concurrent running tasks at scale without scheduler
induced jitter.

Tasks is focused on accuracy of task execution. To do this each task is called within it's own goroutine. This ensures
that long execution of a single invocation does not throw the schedule as a whole off track.
Expand Down Expand Up @@ -89,3 +90,4 @@ if err != nil {
// Do Stuff
}
```

5 changes: 3 additions & 2 deletions tasks.go
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
/*
Package tasks is an easy to use in-process task scheduler for Go. Focused on interval based execution, Tasks
provides both recurring and one-time task scheduling.
Package tasks is an easy to use in-process scheduler for recurring tasks in Go. Tasks is focused on high frequency
tasks that run quick, and often. The goal of Tasks is to support concurrent running tasks at scale without scheduler
induced jitter.
Tasks is focused on accuracy of task execution. To do this each task is called within it's own goroutine.
This ensures that long execution of a single invocation does not throw the schedule as a whole off track.
Expand Down

0 comments on commit 61fc0cf

Please sign in to comment.