the power of 0ne

Ever wonder what happens if you VNC from computer A to computer B, then from inside computer B VNC back to computer A? Looks like Jon has ;)

It's my darling sister's 22nd birthday today! Happy birthday Kt :D

Steve just wrote his first Usertalk script, and it's a one-liner, cool!

But here's a tip: currently you have it setup to so that the script is run by the scheduler, which has a couple of disadvantages:

1. There is probably a lag in between when you update the story and the time the sheduler runs the script and the file is updated on your local machine. The ideal case would be to have the script run every time the script updates.
   
2. Since the scipt is run by the scheduler it is probably running several times a day, it is unlikely that the Manila story has been updated between every interval, which means the script is running when it doesn't have to. Not the most efficient case.

Ok so now you know why the scheduler isn't the most efficient way to run the script, but what is? The answer: callbacks. Callbacks are a wonderful tool that allows you to have a script run after a certain action has been performed, such as a when a story is changed.

Great you say, but how do I get the callback running on my Manila server to talk to my Radio server? The answer? Use an XML-RPC responder on the Radio side :) Ok i'll admit using a callback and a responder is much more complicated than using the scheduler, but there is a lot of power here and once you've seen the power that callbacks and responders provide, there is no going back!