During the intial design stages of a project it would be useful to know what aspects of the AFCS are the most network intensive, and perhaps the most likely areas to cause delayed collaboration responses. I am asking this because there seems so many tempting 'rich' interactions made readily available through AFCS.
For example does video streaming take a lot of resource or is it tracking all the interactions on a whiteboard? Or is it the voice transmission?
I realise it depends on how many users are interacting, for example 100 people chatting might take more resource than streaming one videocam. A rough idea would be useful for somebody like me who has not got any idea what data is being transferred in the background. Otherwise I could assume that I can chuck every pod going into an app and expect it to run smoothly - maybe it would? I have already mentioned on the forum that I personally cannot get the 'You tube Living Room' example to fully initialise without crashing my browser.
Is such a list possible to determine? Is it a stupid consideration?
I should really accept the idea that Adobe is offering a super collaboration server that can handle all this data transfer and I don't really need to think about. I need to forget about the restrictions on my own little server....... and think BIG!
BTW: I am not planning the next killer social application.