Another solution, following along these lines... If the classroom network has a shared drive, then you can use tcp connections to send a message to each computer that simple says "refresh now" or something like that.
Each client computer, upon receiving that message, would then refresh the stack from the shared drive. This might not be as interesting as the other approaches, but would be very easy to do. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Wieder Sent: Wednesday, October 26, 2005 3:08 AM To: How to use Revolution Subject: Re: OpenSockets and multiple stacks...? Alex- Tuesday, October 25, 2005, 5:52:12 PM, you wrote: > The other option would be to do it as a peer-to-peer distribution using > local repeaters - an even more interesting protocol design problem, but > probably even less pragmatic a choice :-) Another way to tackle this would be to have the student stacks "subscribe" to the instructors stack by opening socket connections. Then the instructors stack could just push out messages to the subscribed sockets. This would save you from having to use multicast packets and give you a finite and known pool of sockets to deal with. (Although the peer-to-peer approach is most definitely the more interesting way to go about designing it). -- -Mark Wieder [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
