On Thursday 04 May 2006 23:20, Matthew Toseland wrote:
> Plugins are bad because they work through HTTP. HTTP is bad UI. Thus
> saith Ian, anyway. You can make the engine a plugin, but you need a
> Swing GUI as well.
HTTP-wtf? Where does HTTP come into play if I build a plugin
architecture into my application? :)
I'm talking about plugins that search and index stuff. For example,
somebody might pull frost messages off Freenet and return offered
files. No HTTP and no GUI at all.
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/tech/attachments/20060505/4bdd205b/attachment.pgp>
