Yes, it should. The HTML5 workers have this property, btw.
On Thu, Sep 11, 2008 at 5:10 PM, Nigel Tao <[EMAIL PROTECTED]> wrote:
> So, I'm thinking of adding an origin property on the workerpool, so
> that you can, in a worker, do things like
> google.gears.workerPool.onmessage = function(a, b, msg) {
> if (msg.origin != google.gears.workerPool.origin) {
> return;
> }
> google.gears.workerPool.allowCrossOrigin();
> // do more stuff
> }
>
> This is trivial to implement, since every gears module knows its own
> SecurityOrigin (via its ModuleEnvironment).
>
> Any comments? One thing is that, IMHO, an origin is more a property of
> the factory than a workerpool (and that allowCrossOrigin should have
> been a method on a GearsFactory, not a GearsWorkerPool), but since
> allowCrossOrigin is already on a GearsWorkerPool, I thought to keep
> the origin property on the same thing.
Perhaps implement the same Location object that HTML5 workers have? I
know it's a PITA to implement a new module.
- a
