<br><br><div><span class="gmail_quote">On 1/8/08, <b class="gmail_sendername">Balinny</b> <<a href="mailto:balinny@gmail.com">balinny@gmail.com</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;">
Yousef Ourabi wrote:<br>> Let me start off by saying I believe the new client for Unix like<br>> operating system should be written in a dynamic language such as perl,<br>> python, ruby, or even all of the above...
<br>There's no point in doing so. Make an API in agnostic C / C++. All those<br>languages have bindings with C libs. Then you python app could vary from<br>a call to DoAllStuff() to doing each of the steps with at a lower level.
</blockquote><div><br>It depends on what you are optimizing for. Yes, all those languages have the facility for c-bindings / extensions. But that means you have to re-compile the extension for every platform, vs having a pure python implementation that is guaranteed to work any where python works (cell phones, pda's...etc)
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> As I sit here, typing into this gmail inputbox via Firefox after just<br>
> finishing my rant on why the client should be written in a dynamic<br>> language -- the thought occurs to me that perhaps the notion of a<br>> native client is very 90's and what we should really be thinking about
<br>> are browser extensions that implement the same functionality if not more.<br>><br>> [[ Disclaimer: this is not an original idea, I believe the Heretix<br>> folks are or were up to something similar with the "Monkeys" project
<br>> if memory serves correctly ]]<br>><br>> Think of this:<br>> A Firefox plugin that meets current functionally (gets list of URIs,<br>> crawls, creates ARC, puts to grub.org...)<br>> But also (with user consent / warning) registers new urls with the
<br>> grub server<br>Having the work done with Firefos is a swift knife, very nice but you<br>can get cut.<br>You can be crawling what the user browses with no overhead (just the<br>upload, you are already downloading it). The user finds new urls for you.
<br><br>Some things you need:<br>*Very strict following of Cache directives, Vary, Cookies, HTTP<br>authentication...<br>*Easy button to toggle crawling/not crawling.<br>*Remove from crawled data before sending (error in configuration, spam
<br>site...).<br>*Blacklist of sites to crawl.<br>*Ability to execute in XULRunner<br><br>Some sites you wouldn't want to get crawled under your nick:<br>*<a href="http://somepornsite.com">somepornsite.com</a> Typical example
<br>*<a href="http://myemployer.com">myemployer.com</a> It's not of your interest who i work for.<br>*<a href="http://searchingjobs.com">searchingjobs.com</a> My employer wouldn't like this.<br>*search queries Note they're usually cacheable!
<br>*etc.</blockquote><div><br>I agree with a button for turning off crawling but that is it.<br> <br>After giving the user clear and adequate warning / explanation we should crawl every site he browsers. <a href="http://Somepornsite.com">
Somepornsite.com</a> could be a legitimate search result for some one. In short, the plug-in will not be forced on users, they have to seek it, nor should we baby sit them. If they browser porn, we spider porn. <br><br>I don't see where Xulrunner comes into this, Xulrunner is firefox without Gecko -- so people are not browsing around with Xulrunner anyway....? Unless I'm missing something big?
<br><br>just my 2 cents.<br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">_______________________________________________<br>
Grub-dev mailing list<br><a href="mailto:Grub-dev@wikia.com">Grub-dev@wikia.com</a><br><a href="http://lists.wikia.com/mailman/listinfo/grub-dev">http://lists.wikia.com/mailman/listinfo/grub-dev</a><br></blockquote></div>
<br>