Request for new forum

Quote:

---

Originally posted by souldog
Maybe, but it will loose its focus if material of too high a level is included. Focus should be on the API stuff and maybe even
restricted to C++/C.

---

If we restrict like that there won't be enough posts in the forum and the forum will become unpopular. CG gets more MFC related socket questions. Let others answer. We can tell them to use APIs instead.:D

To Brad!
How come I didn't get notifications for Souls 2 posts? I was viewing Andys post as soon as I got the notification. Then the page was like that. (I didn't refresh)

I also agree, that a forum specialization might be indeed helpful. However, as being mentioned earlier I would rather like to see a common Network forum (just like the common Graphics forum) instead of limiting it to windows sockets.

The following statement is going to sound goofy:

The broader you can make your forum on a specific topic, the greater the probability the forum will succeed.

This is what a couple of people have been saying - pick an area that is broad enough to interest people, yet specific enough that people will know what it is - versus other forums.

C++ Network programming
This forum is for covering network programming, socket, blah, blah, and related networking topics.

Debugging and Optimization
This forum is for covering debugging issues, optimization, and related topics.

These topics are broader than "Sockets" and "Debuggers"; however, they encompus those topics. Additionally, while they are broader, they provide an area where the focus of the questions will be similar. Finally, while specific, these two are broad enough that they may draw several people into posting.

We've not added a lot of forums for a while, so I am willing to add a couple of new forums to break out the VC++/C++ topics. The two above seem like good choices (although better descriptions than mine would need to be added). Are they, however, the best choices for new forums? Additionally, if I add them, then I'd like to have a volunteer to agree to moderate them. This person would probably want to also spend time in the main forum to redirect some of the posts there into the new forum(s).

If the forums don't get used for a while, then we will roll them back into the main forums.

Thoughts?

Brad!

Yes, I thought of these two forums you have described while writing my previous response as well. A third forum I would like to suggest is

Multithreading
This forum is for covering multithreading issues and related topics.

As you already might have guessed, I can moderate these three forums if you want.

Hi,


I think a network forum might be helpful and maybe it could include all types of communications protocols like USB, firewire and even RS-232 and parallel port as well (just a thought).

I think that the multithreading forum is a great idea.

There also seems to be may questions relating to file I/O as well.

TDM

Quote:

---

Originally posted by TDM
I think a network forum might be helpful and maybe it could include all types of communications protocols like USB, firewire and even RS-232 and parallel port as well (just a thought).

---

Well...I would think that integrating USB, firewire and RS-232 would be misleading in regard to a network forum, simply because they are serial communications which are not done through network hardware. Same applies to parallel communications. This is of course my opinion.

Quote:

---

Originally posted by TDM
There also seems to be may questions relating to file I/O as well.

---

I agree that this would be a possible forum as well, however I am not sure at the moment whether the number of questions in regard to this justify a dedicated forum yet...

Quote:

---

Originally posted by Brad Jones
The following statement is going to sound goofy:

The broader you can make your forum on a specific topic, the greater the probability the forum will succeed.

This is what a couple of people have been saying - pick an area that is broad enough to interest people, yet specific enough that people will know what it is - versus other forums.

---

I don't know if it sounds goofy, but I know what I am talking about.

The topic winsock itself is very broad. You have BSD(unix), winsocket and in winsocket you have MFC, API, then you have raw. In APIs you have different IO models (blocking, non-blocking, select, asyncselect, eventselect, overlapped io, iocp) and there are others like Service Providers (LSP comes here). See...these topics can be made to different forums provided it is popular enough (outside CG). My view was rather than making a forum for one (or more) such sub categories include all these into one forum.

Well, if the options are reduced to what Brad! suggested I would suggest to take the word c++ away and have the name Network programming. I don't know if there is any c++ specific Network programming.

Quote:

---

Originally posted by Mathew Joy
Well, if the options are reduced to what Brad! suggested I would suggest to take the word c++ away and have the name Network programming. I don't know if there is any c++ specific Network programming.

---

Well...I think it was meant to indicate that the new forum will be 'outsorced' from the C++ forums and not the others (e.g. Visual Basic)... :cool:

Quote:

---

Originally posted by Andreas Masur
Well...I think it was meant to indicate that the new forum will be 'outsorced' from the C++ forums and not the others (e.g. Visual Basic)... :cool:

---

Is it necessary, since it comes under the Visual C++ and C++ programming category?

Quote:

---

Originally posted by Mathew Joy
Is it necessary, since it comes under the Visual C++ and C++ programming category?

---

Well...I would say no....but you know... :cool:

Nevertheless, I do not think that this would be a big deal whether it will be named simply 'Network programming'... ;)

I agree that multithreading and networking/sockets are two very common question areas, and hence both might benefit from their own forums.

It would be great if Andreas would moderate these forums.

Brad, I wouldn't call the second "C++ Networking", however, since it might imply (especially to newbies) that if the program is MFC-based then the question doesn't belong there but rather should be posted in the MFC forum. Just call it "Networking" and of course explain that it covers all aspects including raw sockets, Winsock API, BSD sockets, MFC-based CSocket and CAsyncSocket etc. I don't think USB, RS-232 and others belong there.

-Mike

Quote:

---

Originally posted by Brad Jones

Debugging
This forum is for covering debugging issues
Brad!

---

all your crash are belong to us. Now that is a broad subject, because as you know, all your crash are typically because they are not using the api's correctly or whatever have you.

I'd have to say there is more my code crash posts than any other. My code don't work right posts, my code blah blah. I think that's too broad.

you could probably replace the visual c++ bugs and fixes forum with this, when is the last time someone posted in there, and most of the posts are people saying I found a bug in MFC or this api...yep you sure found a bug in your own code.

I created two of the forums yesterday. Let's see how they go. If you guys want the debugging type forum or a "Fix My Code" type forum, let me know (yes, these are two totally different types of forums). We will then need to determine the best name and description.

Brad!

I would suggest a change to the description of the Networking forum so that it doesn't say "blah blah". Maybe something like

Quote:

---

This forum covers all aspects of network programming, including raw sockets, Winsock API, BSD sockets, MFC-based CSocket and CAsyncSocket etc., and other network-realted topics

---

"Blah blah" might give an unprofessional veneer to the forum.

-Mike

Quote:

---

Originally posted by MikeAThon
I would suggest a change to the description of the Networking forum so that it doesn't say "blah blah". Maybe something like

"Blah blah" might give an unprofessional veneer to the forum.

-Mike

---

That is what I get for creating new forums at near midnight on a long day...... Doh! :D

I'll go fix that now......


Brad~