Google Git
Sign in
apache / tcl-rivet / 47e58cd8440de46160d6c2ac64ea1683c41469cd
commit47e58cd8440de46160d6c2ac64ea1683c41469cd[log] [tgz]
authorMassimo Manghi <mxmanghi@apache.org>Tue Aug 06 00:40:42 2019 +0200
committerMassimo Manghi <mxmanghi@apache.org>Tue Aug 06 00:40:42 2019 +0200
tree5f206f9fd08269a3d08854955c41c9a689dedb20
parent0e48c266beccccc808780d38d7d7ec5cd15df9ab [diff]
documenting directive SingleThreadExit
5 files changed
tree: 5f206f9fd08269a3d08854955c41c9a689dedb20
  1. cmake/
  2. contrib/
  3. doc/
  4. m4/
  5. rivet/
  6. src/
  7. tclconfig/
  8. tests/
  9. .appveyor.yml
  10. .gitignore
  11. acinclude.m4
  12. BUGS
  13. ChangeLog
  14. CHANGES
  15. configure.ac
  16. cvsversion.tcl
  17. form.txt
  18. genconf.sh
  19. INSTALL
  20. LICENSE
  21. Makefile.am
  22. NOTICE
  23. README
  24. README.configure
  25. README.freebsd
  26. README.MacOSX
  27. README.md
  28. STATUS
  29. TODO
  30. VERSION
README.md

Rivet Logo Apache Rivet

Apache Rivet is a powerful, flexible, consistent, fast, and robust solution to creating web applications with the help of the Tcl language and Apache HTTP Server.

See the doc/html/installation.html directory for installation and usage instructions.

See INSTALL for brief installation instructions - although the above docs in HTML are more thorough and extensive.

See LICENSE for licensing terms.

Current Travis/AppVeyor CI build status for Rivet:

OSMaster BranchRelease BranchBranch ‘winbuild’
Linux 64, Apache 2.4.37, Tcl/Tk 8.6
Windows 64, Apache 2.4.37, Tcl/Tk 8.6.7Build status
fork: Build status		Build status
fork: Build status
macOS 64 (Darwin), Apache 2.4.37, Tcl/Tk 8.5

KNOWN PROBLEMS

  • Rivet is reported to conflict with cgi scripts on some Linux machines. Symptom of the problem is when cgi scripts hang forever and don't send contents to the client

RIVET NAMESPACE

  • With the intruduction of the ::rivet namespace the command set has been moved into it and each command should now be fully qualified. Building rivet you can choose in case to place the commands on the export list or even automatically import them into the global namespace. This is a deprecated option though unless you have a compatibility issue with existing legacy Rivet based code.