MarkBennett / announcer

TODO: one-line summary of your gem — Read more

This URL has Read+Write access

Updated the README to describe what Announcer does

Sun Oct 04 17:58:22 -0700 2009

commit 3fdac317fe979e3ae9320ec3eb06aa09091f179f
tree d862ae59fc10f518c35d5629409fd6e438f5720c
parent 2ad28f9a408206e620306772d948915535ba3a3a

announcer /

name	age	history message
.document	Sun Oct 04 17:51:17 -0700 2009	Initial commit to announcer. [MarkBennett]
.gitignore	Sun Oct 04 17:51:17 -0700 2009	Initial commit to announcer. [MarkBennett]
LICENSE	Sun Oct 04 17:51:17 -0700 2009	Initial commit to announcer. [MarkBennett]
README.rdoc	Sun Oct 04 17:58:22 -0700 2009	Updated the README to describe what Announcer does [MarkBennett]
Rakefile	Sun Oct 04 17:51:17 -0700 2009	Initial commit to announcer. [MarkBennett]
lib/		Loading commit data...
test/

README.rdoc

announcer

Announcer allows you to easily share services and applications without the use of a central DNS server or search engine.

Services are announced using the Zeroconf specification. (See en.wikipedia.org/wiki/Zeroconf)

Fork the project.
Make your feature addition or bug fix.
Add tests for it. This is important so I don’t break it in a future version unintentionally.
Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but
```
 bump version in a commit by itself I can ignore when I pull)
```
Send me a pull request. Bonus points for topic branches.