Quoting Christopher Case <[EMAIL PROTECTED]>: > Oh, once it's done. Though, actually a bit of a discussion now wouldn't > hurt. Basically, the idea is that enet has good documentation, a decent user > base (look at their mailing list archives.), and in general seems all one > could want in a UDP library. It's more actively developed then HawkNL, and > seems to be a bit easier to use. We plan on building a CS plugin that simply > exposes it's interface in a nice CS style way, and for a bonus we'll include > a test app. (More then likely a chat app. No networked walktest, sorry.) >> From this base, we'll build a set of CEL property classes that will allow > entities to share behaviours in a client/server situation, along with some > property classes for handling secure server communication, spoof protection, > and just about all the things you'd want in a modern MMO game. (It could be > used in a more basic setting, sure. We'd be descussing reasonable defaults > and feature lists once the CS plugin was done.) > > That is it, in a nutshell. Sound interesting? > My main view is still that networking does not belong in CS, independent of which library you wrap. It might be ok to place in CSEXTRA (or csexternal). On the other hand it might make sense to include the CEL prop-classes in CEL (that i have no idea about, you have to ask the CEL people;) so maybe the network abstraction should also be in CEL or possibly CS main repo...
-M ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
