mainpage.dox 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. /** @mainpage enet
  2. <center>http://enet.cubik.org</center>
  3. <hr>
  4. ENet's purpose is to provide a relatively thin, simple and robust
  5. network communication layer on top of UDP (User Datagram Protocol).
  6. The primary feature it provides is optional reliable, in-order
  7. delivery of packets.
  8. ENet is NOT intended to be a general purpose high level networking
  9. library that handles authentication, lobbying, server discovery,
  10. compression, encryption and other high level, often application level
  11. or dependent tasks.
  12. @ref Features
  13. @ref SourceDistro
  14. @ref Installation
  15. @ref Tutorial
  16. @ref MailingList
  17. @ref Extending
  18. @ref FAQ
  19. @ref License
  20. */
  21. /**
  22. @page SourceDistro Source Distribution
  23. You can retrieve the source to ENet by downloading it in either .zip
  24. form, .tar.gz form, or accessing the cvs distribution directly.
  25. The most recent CVS can be downloaded <a href="http://enet.cubik.org/download/enet.tar.gz">here</a>
  26. To access ENet via anonymous CVS, you must use the CVSROOT
  27. :pserver:anoncvs\@sferik.cubik.org:/home/enet/cvsroot with an empty
  28. password.
  29. @code
  30. $ cvs -z3 -d :pserver:anoncvs@sferik.cubik.org:/home/enet/cvsroot login
  31. @endcode
  32. Hit the return key when prompted for a password.
  33. @code
  34. $ cvs -z3 -d :pserver:anoncvs@sferik.cubik.org:/home/enet/cvsroot co -l .
  35. $ cvs -z3 co enet
  36. @endcode
  37. This will create a CVS directory in the current directory, and with
  38. the second command will proceed to check the enet module out of CVS.
  39. Any problems with CVS access or request for write access should be
  40. sent via email to @ref MailingList.
  41. */
  42. /**
  43. @page Extending Extending and Modifying ENet
  44. Since ENet is distributed in source form, you can easily extend and
  45. modify it to suit your needs. For example, some users prefer to use
  46. their own memory management routines and can thus replace the
  47. appropriate functions in memory.c
  48. */
  49. /**
  50. @page MailingList ENet Related Mailing Lists
  51. The <a
  52. href="http://lists.cubik.org/mailman/listinfo/enet-discuss">
  53. enet-discuss</a> list is for discussion of ENet, including bug reports
  54. or feature requests.
  55. The CVS commits are also sent to <a
  56. href="http://lists.cubik.org/mailman/listinfo/enet-cvs">enet-cvs</a>,
  57. so feel free to subscribe if you want to keep up with the latest
  58. developments.
  59. */