[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: new version question
- From: Jim Mathies <Jim@...>
- Date: Fri, 21 Apr 2000 13:57:02 -0400
How big are the objects? If they are big - put them in objects -
class instantiated instances of multistate Lua. Then
write a communications layer between them, where
objects can communicate using TCP, or C or whatever.
You control the security of what they access. Standardizing
on some sort of RMI would probably make things
easier to develop over time. Write once and use over
again and all that.
FYI - for what is worth, I'm working on a complete
TCP/IP wrapper for Lua.
From: Martin Dvorak [mailto:email@example.com]
Sent: Friday, April 21, 2000 1:43 PM
To: Multiple recipients of list
Subject: RE: new version question
> If you put a hook on the globals table to prevent those objects
> from accessing it, and don't give those objects any pointers to
> objects(tables) that you don't want them to have access to, they
> should be effectively isolated even if they were all in the same
> Lua state.
I know about this, but it's not what I want to do. I really need
each object to have its own environment, for many reasons. For
example to be able to cut any object off (destroy their state)
anytime I need.
So, I really need to create some kind of communication center
in C which will handle requests from environments to access
variables in environments of other objects. Or does it sound
like a really bad idea?