I think Nitro should stay limited to Web stuff ... maybe it could be extended to some ponctual non-web job but it is essentially a web framework.<br><br><div><span class="gmail_quote">On 2/3/07, <b class="gmail_sendername">
Jonathan Buch</b> <<a href="mailto:john@oxyliquit.de">john@oxyliquit.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>> Is Nitro limited to Web stuff? Could I not have URIs with my own<br>> protocol (e.g., jgb://some-stuff ) and teach Nitro to Do The Right<br>> Thing when it sees it?<br>><br>> I think I tend to think of Web apps (or apps in general) as "fetch this
<br>> resource, do something with it, and pass it on." Often it involves<br>> http:// , but not always.<br><br>yes, I do think that Nitro is limited to Web stuff. At least at the<br>moment. I'm not sure how hard it would be to write a 'adapter' like the
<br>CGI one, just for another type of 'getting called'. I don't think<br>it would be particularily hard, but all the "mechanisms" within Nitro<br>are of course quite 'web centered'.<br><br>Somebody might prove me horribly wrong when I say this. :)
<br><br>Anyone have an idea of a protocol which would fit into the Nitro 'range'<br>of working with things? I'd really be interested to hear one. :D<br>(Nitro, going general purpose!)<br><br>Jo<br><br>--<br>Feel the love
<br><a href="http://pinkjuice.com/pics/ruby.png">http://pinkjuice.com/pics/ruby.png</a><br>_______________________________________________<br>Nitro-general mailing list<br><a href="mailto:Nitro-general@rubyforge.org">Nitro-general@rubyforge.org
</a><br><a href="http://rubyforge.org/mailman/listinfo/nitro-general">http://rubyforge.org/mailman/listinfo/nitro-general</a><br></blockquote></div><br>