When I refer to a browser I'm just talking about the IP camera. Since that's kind of 'outside' of my control system it's a different communication protocol and kind of separate issue.
My design could have a browser window in the application but the cheap camera I'm using for tests only works in Internet Explorer so I'm keeping it separate. Mine (at least right now) is two different things: 1. A browser window that shows what the IP camera is sending back and 2. An interface that sends signals to the Arduino on a different IP address. The Arduino can also forward instructions to the IP camera for pan and tilt by IP or just control a servo if I go that way with it, I'm still not sure. But however it ends up, I think it will be a webcam for video and a different independent setup for the controls.
I like your plan (because it's the same way I did it.
![Smile :)](./images/smilies/icon_e_smile.gif)
That's an interesting plan for the com signals. I would like to check out the code.
I went a different way with mine, thinking I should only send things over the wire if they changed state. I'm determining what a 'button 2' means and what to do about it in the Arduino so the PC-side is really generic.