Hello Randall,
> If your application is client/server, you really should just go with an > ordinary TCP connection (or, conceivably, a UDP port), define a proper > protocol and do the whole thing properly. This makes sense (if done right, the submitter can be invoked several times in parallel and submit more than one e-mail in parallel to the daemon - and this is needed). > Realistically, I'd start by looking at the ordinary Servlet / > HttpServlet mechanism. You get so much from existing servlet containers > (Tomcat, Jetty, GlassFish, etc.) that it's very hard to justify > starting from scratch. Will see if I learn how to deploy clojure application in a Tomcat container... > Named pipes have peculiar semantics and, of course, do not cross machine > boundaries (unless you're running in one of the now-rare distributed > Unix kernels—I say this as a one-time employee of Locus Computing > Corporation...). I can't say named pipes really useful for much other > than their use by shells for their <( command ) syntax. So it looks that named pipe does not cut it here. Thanks for all the info, and I can proceed in other way(s) now... But would you not expect that the working code still works when enclosed in the "while" construct? Kind regards, Vlad --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
