I can only recommend getting familiar with the XMLRequest and
WinHttpRequest objects (they share lots of functionality), Ajax and
PHP. Since you're already proficient with JavaScript, the request
objects should be very easy. Examples abound on the internet. PHP is
also quite an easy language imo. The problem is that if you go the
XMLRequest/Ajax route, you'll hardly make it without learning PHP at
the same time, Ajax being the client-side code, while PHP being the
server-side.
Getting the basics of these nailed down will get you a long way.
I know no other use of an apache server than everything I already
mentioned, unfortunately.
> Using your filenames as an example, if I needed to update async.js, I
> can't do it when XSI is loading because async.js will be executing. The
> only other time I can pull the latest version of async.js and not get in
> the way of the user would be when XSI terminates. I can then unload the
> plugin manually from XSI and replace it. Next time XSI starts, it will
> use the new version of async.js. This is useful for occasions where the
> production pipeline changes affecting tool delivery.
The idea is to never have to update the async.js plugin. Once it's
written, tested and deployed, it must be only in the most major
circumstances that this specific plugin should be updated. Only other
plugins are updated. Again, using LoadPlugin()/UpdatePlugins() through
a loader plugin should completely eliminate the problem.
Bernard
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
