So I assume XMPP and AMQP would be other sinks / sources? If so the mind is boggling with old ideas laid to rest for some time...
A thought that comes to mind is that of a source and sink are of the same type, eg. AMQP, would the interconnection make use of that technologies underlying implementation. eg. AMQP exchanges? Time to check out the progress in git... Marc On 18/08/2009, at 3:20 AM, David Pollak wrote: > With Goat Rodeo, you can define message flow with an abstract source > (input) and sink (output) in the form: > > Foo %> Bar %> (Baz * Distribution) > > You can define fork/join constructs, tee constructs, etc. in the > high level flow description. The flow description defines the type- > safe progression from each logic unit. The location of each logic > unit and the threading/transport model is decided at runtime. This > means that you can define logic models and plug in an "Akka > distribution and threading" strategy for production or a "single > threaded" strategy for your local test harness. > > You'll also be able to register the composed modules that can be > composed into larger flows. > > So, how does this work with SOAP? Well.. the SOAP piece is just a > source and sink for the logic flow. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
