search

saolsen / floclo

Floclo watches a flowdock chat room and evaluates clojure expressions tagged with #clj
5 stars 2 forks source link

Design a plugin system #3

Closed jeremyheiler closed 10 years ago

DarrenN commented 10 years ago

@jeremyheiler Could we use this to define macros/functions to use within floclo in a safe manner?

saolsen commented 10 years ago

Yeah probably but there are better ways to add custom clojure macros. Plugins are more for non clojure things that floclo would do. Like launch nukes or run things through marksy.

jeremyheiler commented 10 years ago

Probably not. Maybe we can create a fresh environment per thread. This would mean every non-thread message would have its own environment to define global state. On Dec 20, 2013 8:11 PM, "Darren_N" notifications@github.com wrote:

Could we use this to define macros/functions to use within floclo in a safe manner?

— Reply to this email directly or view it on GitHubhttps://github.com/saolsen/floclo/issues/3#issuecomment-31053109 .

saolsen commented 10 years ago

An environment per thread would be super dope! Lets definitely do that! (making another ticket for it) https://github.com/saolsen/floclo/issues/12

jeremyheiler commented 10 years ago

When a message comes in, should it be broadcasted to all plugins simultaneously, or should there be a "pulgin pipleline" that can inspect the message, and potentially stop it from propagating any further?

DarrenN commented 10 years ago

What about a pubsub environment where plugins "subscribe" to floclo for specific tags, or where we thinking this could expand beyond hooking into tags and just parse all text coming through the system?

jeremyheiler commented 10 years ago

DONE