2 ms·

Thanks. I was also in the discussion. When CLIPS is used as an expert system shell, then performance comparisons are pretty restricted. But since you have seeme

by Rochus 2y ago

Thanks. I was also in the discussion. When CLIPS is used as an expert system shell, then performance comparisons are pretty restricted. But since you have seemed to use it more for "indexing" and "caching", which is a domain shared by other interpreters used for the web, a performance comparison seems more feasible, especially if you already have implemented such features with other interpreters as well.

ryjo 2y ago
So you were! I apologize for my oversight. > you have seemed to use it more for "indexing" and "caching", which is a domain shared by other interpreters used for the web That's the idea! I think CLIPS is a good framework for a generic run-loop (or `while` loop). If you can conceptualize your app as such, you can reap the benefits inherent in the rete algorithm within your application logic. To see what I mean, take a look at the tcp server in the CLIPSockets repo: https://github.com/mrryanjohnston/CLIPSockets/blob/6.4.1/examples/server-complex.clp https://github.com/mrryanjohnston/CLIPSockets/blob/6.4.1/exa... UPDATE: I edited the link to point to the 6.4.1 tag version of the repo. The `main` branch is using the latest (7.x) from CLIPS svn as the base. UPDATE2: I edited my previous comment to specify that it is a tcp server, not an http server.