Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 23191 invoked from network); 26 Sep 2008 14:17:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Sep 2008 14:17:23 -0000 Received: (qmail 27536 invoked by uid 500); 26 Sep 2008 14:17:19 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 27071 invoked by uid 500); 26 Sep 2008 14:17:18 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 27062 invoked by uid 99); 26 Sep 2008 14:17:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2008 07:17:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.44.16.11] (HELO getopt.org) (69.44.16.11) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2008 14:16:17 +0000 Received: from [192.168.0.220] ([81.219.54.251]) (authenticated) by getopt.org (8.11.6/8.11.6) with ESMTP id m8QEGvU03955 for ; Fri, 26 Sep 2008 09:16:57 -0500 Message-ID: <48DCEECA.40100@getopt.org> Date: Fri, 26 Sep 2008 16:16:42 +0200 From: Andrzej Bialecki User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: java-dev@lucene.apache.org Subject: Re: RMI, Searchable and RemoteSearchable References: <1FD75988-CBA0-4B1C-8681-159138885F0C@apache.org> In-Reply-To: <1FD75988-CBA0-4B1C-8681-159138885F0C@apache.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Grant Ingersoll wrote: > Came across: > http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fgroups.google.com%2Fgroup%2Fandroid-developers%2Fbrowse_thread%2Fthread%2F601329551a87e601%2Fcd0919ce891b4a26%3Flnk%3Dgst%26q%3Dlucene&ei=zNzcSPHCF4yI1ga61YiTBA&usg=AFQjCNECrBnNPBkxI4I0EbIzI-mNp3S4YA&sig2=4sDMmwa9Mrk38Nla_ULtOg > > > The gist of it is, that on Android doesn't provide the RMI package. > Thus, Lucene core can't work on Android b/c of Searchable extending > java.rmi.Remote. > > This has always seemed a little weird to me. I'm no RMI expert, but > couldn't we drop the extension on Searchable, and add it to > RemoteSearchable, and then move RemoteSearchable and all the RMI stuff > to a separate contrib? This, in my view, would be consistent with > keeping core, core, since not many people, I think, even use the RMI > stuff and it certainly isn't required in most cases. > > I haven't looked into what would break in doing it, so it is just a > suggestion at this point. Seems like it could be "mostly" > back-compatible, though, since we would just be requiring someone to get > the new JAR, unless of course they implemented their own extension of > Searchable that relied on the Remote marker interface. > > Thoughts? Even more, I wonder how many people use RemoteSearchable in real applications. If it's in a relatively small number of cases, then let's move it to contrib - so long as we remember to keep all search-related core classes Serializable ;) I recall a single situation when I had a use for remote searchable, and due to the operational issues with running rmiregistry we went with a custom RPC anyway. -- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org