Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 53741 invoked from network); 6 Jun 2006 12:47:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jun 2006 12:47:47 -0000 Received: (qmail 24265 invoked by uid 500); 6 Jun 2006 12:47:44 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 24232 invoked by uid 500); 6 Jun 2006 12:47:44 -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 24221 invoked by uid 99); 6 Jun 2006 12:47:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2006 05:47:43 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_00_10,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of simon.willnauer@googlemail.com designates 66.249.92.170 as permitted sender) Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2006 05:47:42 -0700 Received: by ug-out-1314.google.com with SMTP id u2so1716246uge for ; Tue, 06 Jun 2006 05:47:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=ZgSzfcD7muVUY+z3g8R4o3Z9w3xhpPMeF9jqRf/f1KvPOt7eOrskLb6BEctEJtUwUzxejKPaZxEresErslC6tfATTZsfBz7wg4qC6Ksc0RnDJ2NRP8hteKscycmGK3I6w/9OdEnw3khHEoZvhKDH41JTZDM2gsXRqDpHgcWhZw8= Received: by 10.67.105.19 with SMTP id h19mr4456240ugm; Tue, 06 Jun 2006 05:47:20 -0700 (PDT) Received: by 10.66.236.1 with HTTP; Tue, 6 Jun 2006 05:47:19 -0700 (PDT) Message-ID: Date: Tue, 6 Jun 2006 14:47:19 +0200 From: "Simon Willnauer" Reply-To: simon.willnauer@gmail.com To: java-dev@lucene.apache.org Subject: create feeds in GDATA - Server MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19810_6146316.1149598039042" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_19810_6146316.1149598039042 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, the first version of the GDATA server is already running and it supports all the CRUD actions base on a lucene storage. so the next thing is to enable multiple feed ( I wouldn't be a proper server serving just one single feed instance :). Basically the gdata - protocol description doesn't say anything about inserting new feed instances, the API neither. Lot's of possibilities are around to create an interface for inserting new feeds. XML descriptors per feed could be possible but that could easily become a xml nightmare. So what else could be provided... There could be a SOAP endpoint for creating/deleteing new Feeds or a secondary REST - Based Interface could be provided. This feeds could be stored inside the storage component including user account data (should we provide more than one user account for altering feeds?!). Quiet easy to use would be a administration JSP based component of the server, but guys don't forget I just have 2 1/2 month time ;). No problem doing all these extra features when SoC has finished. --> I thought about a mySQL connector for storing entries and requesting feeds in addition to the lucene base storage and BerkleyDB as well. regards Simon ------=_Part_19810_6146316.1149598039042--