-
amy_murphy changed the TeenyLime 0.1 file release.
2009-06-15 09:00:08 UTC in lime
-
Most likely the path containing the class files for the chat are not in the classpath where you launched Lime. Your error imples that the classloader could not find the class chat.LChat..
Try eihter putting LChat.jar in the same directory where you launch Lime, or set your classpath to include both Lime and the chat bin directory.
It should work.
-Amy.
2005-12-21 15:43:37 UTC in lime
-
Unfortunately, this behavior is the documented "correct" behavior. The version of Lime you are using EXPECTS announced disconnection. If a host does not announce its disconnection, the system does not recover from it.
We actually have another version of Lime that will be released in January. This new version is a rather complete re-work of Lime that handles the kind of...
2004-12-20 16:44:13 UTC in lime
-
If you're asking how matching happens, I suggest reading the LightTS documentation. There is a link from the Lime web pages, or lights.sf.net.
The short answer is that a template is just a tuple with some of the fields formal. So, <string> matches <"foo">. You create templates just like you create tuples with LighTS, and the matches method is well described in the...
2004-12-17 16:03:08 UTC in lime
-
Admittedly I did not read all the output carefully, but the problem is likely the parameter "current" you are using in the rdp operation. You need to use either the AgentLocation (ID) of the host that wrote the tuple or the HostLocation where the writing agent is residing.
Another thing to try is a rd instead of a rdp. Use cur=unspecified in the rd. If this doesn't find the...
2004-12-17 08:14:18 UTC in lime
-
Such an item would be better addressed in LighTS, the tuple space underlying Lime. Then, the persistency of LighTS should be tied into Lime (I think fairly easily).
As far as I know it has not been done.
-Amy.
2004-12-10 09:52:35 UTC in lime
-
First, clarification. inp is allowed inside the reactsTo code only if it is local in scope.
As for your suggestion to throw an exception instead of failing, I can likely add this to the next minor release. I also recently fixed a bug, so a new release should be coming soon (in a week or so).
About a ubiquitous reaction that removes a tuple. That's not something I want to address...
2004-06-14 14:48:56 UTC in lime
-
Your solution with the inp will work! The information that you need IS in the ReactionEvent. re.getSrouce() gives you the Agent ID of the agent that is holding the tuple. new AgentLocation(re.getSource()) should be used as the "current" parameter for the inp. (destination can be unspecified)
Note: you will need to put the inp into a separate thread (similar to what you described...
2004-06-11 09:56:43 UTC in lime
-
Lime itself does not do any form of ad hoc routing. It assumes that you have a routing layer in place that does two things:
1. point to point communication
2. multicast support
If your cluster of handhelds has an ad hor routing stack, then Lime should work. Keep in mind, however, that the current instantiation of Lime either assumes that you declare when a node is within range and when it...
2004-05-06 13:06:11 UTC in lime
-
Yes, -mcast has been removed.
You can still run Lime on a host with no intention to connect it to other hosts by using the -engage explicit flag, and never calling LimeServer.engage.
However, Lime does expect a network connection to be available, and therefore you will not be able to start Lime on a host that is without a network.
Sorry for any inconvenience this may cause...
2004-04-06 15:33:11 UTC in lime
