Be the first to post a text review of Dcon Pro. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• wastingtape takes a bow

  I've uploaded some of the tweaks that i've been playing with recently as 0.0.8b. After a year of development i think i'm retiring from DconPro Hub. *takes a bow*

  posted by wastingtape 1957 days ago

• File released: /dconprohub/0.0.8b-devel/dconprohub-0.0.8b-devel-source.zip

  posted 1957 days ago

• dconprohub 0.0.8b-devel file released: dconprohub-0.0.8b-devel-source.zip

  posted 1958 days ago

• DconPro Hub 0.0.8 Released

  0.0.8 marks the return of DconPro Hub to a true NT service. Batch files are included to easily start and stop the hub.

  posted by wastingtape 2256 days ago

• File released: /dconprohub/0.0.8-devel/dconprohub-0.0.8-devel-source.zip

  posted 2256 days ago

• File released: /dconprohub/0.0.8-devel/dconprohub-0.0.8-devel-setup.zip

  posted 2256 days ago

• Tracker artifact added

  hortongeo created the Crash on Search artifact

  posted by hortongeo 2256 days ago

• Tracker artifact added

  hortongeo created the Title bar artifact

  posted by hortongeo 2256 days ago

• Tracker artifact added

  hortongeo created the Crash on save artifact

  posted by hortongeo 2256 days ago

• dconprohub 0.0.8-devel file released: dconprohub-0.0.8-devel-setup.zip

  DconProHub Change Log http://sourceforge.net/projects/dconpro/ v0.0.8 ------------------------------------- Released 9/6/03 WHAT'S NEW Hub converted into true NT service. Internal Hub object organization was totally redone. DC and Hub objects are now in their own (soon to be remotable) DLL. Hub was updated to better handle disconnect events (individual and hub shutdown) Added "IPAddress" and "Port" properties to user object. Fixed a few spelling errors in the code comments, and commented areas a bit. Hub now (correctly) sends $OpList even if it's blank. Fixed a bug that didn't disconnect users properly. Optimized broadcast code: For loop now keeps track of how many times message has been sent, and if it sends it the same amount as there are users connected, it stops. (as opposed to looping through the rest of the array) Ops and Registered Users now supported properly. KNOWN BUGS If user exceeds ChatLimit, their connection seems to break. CVS code is out of date. $HubIsFull is not yet supported. WHAT'S NEXT Performance and reliablity are still the leading important factors in production. This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.7 ------------------------------------- Released 9/1/03 WHAT'S NEW BIGGEST IMPROVMENT: Performance! The Broadcast network code was modified to efficiently handle the sending of hundreds of messages at a time. The end result is that the hub can now handle hundreds of chatting, searching, and PMing users. Thanks to DCStressor for the testing facilities (http://www.lwave.ca/shasta/). Running on a P4C 2.4Ghz, the hub can handle 250 simultaneous users, with 18MB RAM usage at about 20% CPU. At about 200 users, most clients (NMDC, DC++, etc.) have a hard time, and ofen stop responding. Added some basic statistical reporting to the hub window interface. "Incoming" is the amount of messages that the hub has sucessfully recieved (chat, search commands, etc.) "Outgoing" is the amount of messages that the hub has sucessfully sent out to the users (total). Moved a few things around in config.xml. Hopefully the new formatting will make configuring your hub a more cohesive process. Notes in config.xml will be moved to documentation. I'll leave what is there for the time being. I pretty much re-wrote the Config class (config.vb). It now recursivley searches the XML config data and reacts accordingly. This makes adding new items easier, making nested tags easier to read, and making the "save" code much easier. The warn and kick messages for flooding are now configurable. The name the server uses in chat (formerly <Server>) is now configurable. Added Chat Replay. When a new user connects, the hub will send them the last few lines of chat to "ease" the newcomer into the conversation. The number of previous lines to send is also configurable. Added licensing info to the top of the classes/objects in the source. KNOWN BUGS Client "dies" if they change their username after connecting. When a user connects to hub and his/her username is already in use and the badnick mode is set to "redirect", the hub errors out. If user exceeds ChatLimit, their connection seems to break. Chat Replay does not replay chat sent by that user. I'm not sure if this is a good or bad thing. Flood control, chat replay, server-side timestamp, and other features have been temporarily disabled until further performance issues can be investigated. WHAT'S NEXT Performance and reliablity have become king in the past few months. Some of the features that where added will be re-examined in light of performance issues. Some may be removed. 1.0 is only 3 versions away. Efforts will continue to create a fully working hub. This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.6 ------------------------------------- Released 5/31/03 WHAT'S NEW Hub starts automatically when launched now. If a username is already in use, the hub informs the user and disconnects them. The DConn ojbect (DC protocol handler) was updated to properly use $Hello and $MyINFO. The hub will properly handle user info changes after a user connects (and changes it). The following are now configurable via config.xml: hub name, port, host, maximum connections. Chat properties are now configirable via config.xml: maximum character limit and flooding control. Added an "Offense Limit" whereby users who violate policy will receive a warning which will count as an offense. Once the offense limit threshhold is broken the user will be kicked. Added options to handle the event of a bad/in-use username. Once again see config.xml Hub propertly handles Op connect/disconnect and adjusts NickList accordingly. KNOWN BUGS Client "dies" if they change their username after connecting. When a user connects to hub and his/her username is already in use and the badnick mode is set to "redirect", the hub errors out. If user exceeds ChatLimit, their connection seems to break. WHAT'S NEXT More features Stable hub Flushing bugs out & testing This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.5 ------------------------------------- Released 4/16/03 WHAT'S NEW NETWORK CODE FIXED! *whew* Didn't think this one was ever going to come to a close. It seems the official DC client sent a termination character sort of as a Ping/Pong type thing to make sure it was still connected. The problem was i didn't know about this, and so my code left the termination character on the start of the next message, nerfing all subsequent messages. It has been fixed and the network code seems to be working great! Hub working so far with all tested clients. Let me know if you have trouble conecting with a certain client. -> wastingtape@users.sourceforge.net <- Added a bit of input validation checking to UserManagment class. KNOWN BUGS Suprisingly enough, none that i know of. ;) WHAT'S NEXT Current if data is recieved, and it's not identified to be a command, then by default the server broadcasts the data to the client, assuming that it's chat. I'd like to make this option configurable. Leaving it open of course allows for future protocol expansion or unforseen things. It of course allows a higher risk of spamming or exploit. Now that the network code works correctly, i'm going to be focusing on making sure the protocol implemenation works as expected. I'm going to hold off on the Multi-hub support until after single mode is stable. Once the protocol handling is done i'll be moving to more the Hub's interface and administration code. This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.4 ------------------------------------- Released 1/20/03 WHAT'S NEW UserManagement.vb Class Implmented - Class handles secure management and storage of registered usernames - Class provides framework for authenticating users Added Op support. (login, broadcast, etc.) Added $Kick and $OpForceMove support Made the Uptime label work on the main form KNOWN BUGS The search support is still really fickle. Don't search unless you really have to. I'm still having trouble with the official client temporarily lagging out. It seems to be when it has trouble with the $Search command, it will stop sending messages but will recieve them. This problem only exists with the official client. WHAT's NEXT Get the search working! This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.3 ------------------------------------- Released 1/18/03 WHAT'S NEW Simply put, everything. The hub has been split into two main classes, DConn and TCPServer. See the official website for a description of the interaction between the two. The new architecture allows for a lot cleaner management of what the hub is doing, and is a much better OO design as the objects are self sufficient. Temporarily, the Hub was moved to a Standard EXE format instead of a Windows Services. This has dramatically increased the speed of debugging and been a major help. When a stable beta is released, it will be as a Windows Service. Additionally, the following protocol additions where made. Hub name sent on connect Announces new users as they join Properly handles all user info NickList now works Chat handler written Private messages now work Direct and Passive connections still buggy, but implemented Announces when user quits Bottom Line - The hub actual acts like a hub now, and not an expiremental project. ;) KNOWN BUGS Direct and passive connections are still wierd ($ConnectToMe) For some reason, the official DirectConnect client will "lag out" with the hub. It will stop sending data, and the hub won't send any to it. Occasionally it recovers and all of the protocol up to that point spits out in one massive chunk, but it typically just stops working. DC++ and DconPro clients don't seem to exhibit this behavior. $Key is still buggy. It's currently commented out. WHAT's NEXT I'm still missing a user management system. The hub handles current user info, but i need to devise a secure way to maintain a user database for Ops and admins. Also, the problems with the official client are bugging me. After those issues are resolved, work on administration will begin. Currently the hub is, more or less, unconfigurable. That will change. This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.2 ------------------------------------- Released 1/1/03 WHAT'S NEW Added the following event handlers: $Key $ValidateNick $Version $GetNickList Array of DCUser type has been implemented. This array contains the data of the currently connected users. Lock & Key code works now. File: DCCommands.vb - Contains code to process client and server DC commands. File: DCGeneral.vb - Contains generic DC code. File: DCSecurity.vb - Contains security related DC code. KNOWN BUGS Service does not shut down properly Random crashes after $ValidateNick TO USE Run installer, then right-click on "My Computer" and select Manage. Choose Service, and locate "DconPro Hub" in the list. Push the Play button to start the service. Attach a debugger to it to watch service status. WHAT's NEXt Reliable validation of incoming Nicknames is on the top of the list. I still need to device a user management system which involves the storing of passwords and operator information. This release by T. Stone (wastingtape@users.sourceforge.net). v0.0.1 ------------------------------------- Never released. Source files released. Much thanks to Joel Thoms (www.joel.net) for his "Generic Multi-Threaded TCP Server" code that provided much of the base of this project. Thanks joel! Here's a run down of what each file is: AssemblyInfo.vbAssembly Info for the .NET project file Changelog.txt(this file) DconProHub.slnVisual Studio Solution file for project DconproHub.suoVisual Studio Solution User Options file for project DconProHub.vbprojMain Visual Studio project file (VB.NET) DconProHub.vbproj.userMain Visual Studio project user options file (VB.NET) DCSecurity.vbVB Classfile that will contain DC code relating to security Events.vbA VB class for managing events License.txtA file detailing the license under which this code is distributed Logging.vbA VB classfile for control over logging mechanisms (only half implemented) Main.resxXML resource template for Visual Studio project Main.vbThe main VB file containing service code ProjectInstaller.resxXMl resouce template for project installer ProjectInstaller.vbVB file for handling installation of service service.configAn XML based configuration file. (currently not implemented) TCPServer.vbVB file containing classes that handle the listening aspect of the service TCPServerClient.vbVB file containing classes that handle the client connection aspect of the service ABOUT Nothing really exicting to see so far with this release. Basic TCP connection management is in place. The server will generate a Lock and Pk, send it to the client, and you can see in the event log the client replies with the Key. Code is a bit under commented except in TCPServer.vb and Main.vb. Expect to see all source files as commented as they are. TO USE Compile to exe, then run "installutil DconProHub.exe" from the compiled bin directory. WHAT's NEXt Validate person's nicknames. Figure out if they are an operator or a regular user, and implement a user management scheme. Currently on the table is an array of types that contain the various bits of user info. This release by T. Stone (wastingtape@users.sourceforge.net). "Technology divorced from humanity is worse than no technology at all."

  posted 2257 days ago