1  |   Order by default

Jun 25, 2003, 4:07am

Yes, Miles is right. In fact, you can define your call back functions as
class functions but not as member functions. You can do this by declaring
the function "static". This makes it work like any other function that is
outside the class except for the name scoping. As Miles stated, this implies
you will get no implied "this" object passed in and it will be a true class
only function and not a member function that can act on an object so I
recommend you find the owner object of the event and deliver the message to
the right object. I am not sure this buys anyone anything but you *can*
define call backs in classes just not as member functions.

Enjoy,
Uzume

[View Quote]

Jun 25, 2003, 5:15am

I agree. AWI recently added support for HTTP REFERER. Why not ask that there
be some other world specific data sent in the HTTP request. They could even
support a POST instead of a GET that passes in the world name or something
(though this might be extreme as I think there are other easily accessible
HTTP headers they could add with the world name in it). This would allow the
server to determine the requesting world without changing the URL (which AW
uses as a cache handle).

These are just some hopefully useful idle thoughts.

Enjoy,
Uzume

[View Quote]

1  |   Order by default