I'm not really convinced Felix is a good location for such a project, mostly because the main purpose isn't really related to OSGi (or so it seems) and OSGi looks like just an implementation choice in this case.
On Mon, Sep 13, 2010 at 22:43, Donald Whytock <[email protected]> wrote: > So in general, what are the thoughts of this as a Felix subproject? > Useful as a means of exposing services to users (or other services) > via Parsers? Or too specialized and application-oriented? > > On Mon, Sep 13, 2010 at 4:06 PM, Guillaume Nodet <[email protected]> wrote: >> Not sure which example you're referring to, but the input and output >> are completely decorrelated in camel, so you can mix and match any >> protocol you need with processors in between. I'm sure you'll find >> much more help on camel specific questions on the forums >> (http://camel.apache.org/discussion-forums.html) ... >> >> On Mon, Sep 13, 2010 at 21:58, Donald Whytock <[email protected]> wrote: >>> Thanks...Camel routes look good for building channels on. Do you know >>> if incoming streams absolutely have to bounce through files on the way >>> to processors (as appears in the examples)? And is this the best way >>> to have many streams feed a single processor? >>> >>> >>> On Mon, Sep 13, 2010 at 2:07 AM, Guillaume Nodet <[email protected]> wrote: >>>> FWIW, I've blogged about something slightly related that I did a few >>>> months ago: >>>> http://gnodet.blogspot.com/2009/10/jira-notification-system-for-irc-using.html >>>> It's only slightly related as the aim wasn't to provide a real chat >>>> bot, but using >>>> Camel on top of Karaf made things really easy to do. >>>> Camel is something you may want to look at... >>>> >>>> On Fri, Sep 10, 2010 at 17:52, Donald Whytock <[email protected]> wrote: >>>>> A few months back I'd thought about submitting my Chatterbot project >>>>> to the incubator. Now that I have a fully functional prototype I'm >>>>> considering instead offering it as a Felix subproject. >>>>> >>>>> Chatterbot is built on Felix, designed to accept messages over a >>>>> variety of protocols and submit them to command processors. This >>>>> could serve as a remote-access framework, a chat responder, a chat >>>>> lurker, a cross-protocol message forwarder, and so on. The project >>>>> wiki is at http://www.imtower.net/chatterbot >>>>> >>>>> My thought for adding this as a Felix subproject is that the bundles >>>>> for handling protocols can be generalized to be used outside of >>>>> Chatterbot. The same may be true for the command-processor bundles. >>>>> >>>>> Your thoughts? >>>>> >>>>> Don >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Guillaume Nodet >>>> ------------------------ >>>> Blog: http://gnodet.blogspot.com/ >>>> ------------------------ >>>> Open Source SOA >>>> http://fusesource.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
