Has the application owner defined an interface for long-running components? If not, maybe convince them to. Then they could just (.start yourCode) and then make whatever API calls you have defined, with zero start-up costs per-call from their side.
(This is what I do when integrating non-Clojure .jar files into Clojure applications -- I make them follow the Component[1] model and provide access to whatever connections, config, etc., they need via the Component library definitions.) For your particular case, there are some fun ways in which you can manage state and respond to API calls in a long-running, in-memory Clojure app (in particular, core.async), so this could be a real treat for you :-) Hth, d ---- [1] https://github.com/stuartsierra/component On 21 March 2017 at 12:29, John Gabriele <jmg3...@gmail.com> wrote: > On Tuesday, March 21, 2017 at 11:24:20 AM UTC-4, Michael Lindon wrote: >> >> I wrote a collaborator some clojure code which I distributed to them as a >> standalone jar file which they are executing with >> >> java -jar mystandalone.jar >> >> The problem is that this executable is called a great many times in their >> application and every time the >> executable is called there is a java/clojure startup cost. In fact the >> startup cost heavily domiantes the >> run time, whereas executing the code in a repl is almost instantaneous. >> >> How can I get around this? Would it be better to make a clojurescript >> executable? >> >> > > One way around it might be to write your program as a separate service, > running on the same machine, with it listening for connections on a network > port. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
