Project X development footprint (4)

I haven't updated my blog for several days. I have been thinking about some details of Project X except for the group activities of the Party organization on weekends. MS netmeeting has basically been exclusive to me. First, NetMeeting is basically a completely encapsulated component of H.323. The H.323 protocol details that the audio of a network conference is a mix of multiple audios, video is the first video to establish a connection. It is impossible for one party to accept multiple videos in a meeting. I designed an implementation to create a network meeting between three machines A, B, and C with Win2000 installed. There is a camera on machine A and machine B, and then two browser processes (Net Meeting COM Object in machine C) are enabled simultaneously, because Net Meeting can only run one instance, so it is impossible for you to enable two net meeting processes at the same time, at this time, we can see that the process on the three machines shows the mutual visibility of conference calls, but the key is that the video is the first communication content. Therefore, this solution is unlikely-that is, taking the multi-process approach, while switching Windows processes requires too much resources is also an important issue. To separate multiple videos, I think we can adopt two methods: first, programming the codec of net meeting, that is, the method I mentioned in the previous blog. Second, if I can change the port number of each net meeting instance, then I can separate multiple signals, but this is generally impossible and should be fixed for the net meeting port.

Maybe I will split the H.323 component into several parts to solve this problem.