elementary-dev-community team mailing list archive

[Goncalo Margalho <g@xxxxxxxxxxxxx>]

I say that we should do our own apis, no doubt about it but for a prototype
we can use the provided apis just to see how everything works and if we can
continue with that path.
Then if we decide that is the right path we can put more people working on
it and create something good.
On Mar 26, 2013 3:05 AM, "Chris Timberlake" <game64@xxxxxxxxx> wrote:

> Why not just make a supplemental api?
>
> So you do website.com/followthru/couchbaseshit
>
> And website.com/customapishit/
>
> Then you are essentially having both a crunch base a pi and then a custom
> a pi. It makes no sense to do double the work when someones already done it.
>
> Plus scalability is important if your going to have an app store. At the
> moment appcenter has zero chance of being a real appstore. Couchbase would
> be a step in the right direction in changing that.
> On Mar 25, 2013 5:34 PM, "Goncalo Margalho" <g@xxxxxxxxxxxxx> wrote:
>
>> No what i mean is to do in this way to build a prototype, to see if it
>> works properly, because some people are saying that if we do it online will
>> be very slow. SO we can build a prototype, making the less effort possible
>> (this is why i said to use those APIs to access the DB) and if it works and
>> everyone agrees on how it is then we can work and make real APIs, written
>> in the language that we prefer, around it.
>>
>> I think this software will be the center of everything, so we have to
>> make it very good, fast, easy and full of features.
>>
>> So what do you think on doing it in this way?
>>
>>
>> On Tue, Mar 26, 2013 at 12:28 AM, Joshua Strobl <truthfromlies@xxxxxxxxx>wrote:
>>
>>> A self-build API, in my opinion, allows for more flexibility and
>>> integration with third-party services (such as the Ubuntu Reviews API) than
>>> a generated API from Couchbase. It may not necessarily be easier to
>>> maintain, however we'll be able to add / remove features at our own speed
>>> and not rely on potential breaking changes by Couchbase.
>>>
>>> One could say that we could just stick with a particular version of
>>> Couchbase to ensure things don't break, but that opens up the doors for
>>> future security exploits and vulnerabilities.
>>>
>>> On Mon, Mar 25, 2013 at 5:20 PM, Goncalo Margalho <g@xxxxxxxxxxxxx>
>>> wrote:
>>>
>>> Why should we "waste" time on building an API for it if we could just
>>> build the database with couchbase (which is very scalable as well) and just
>>> use those ones, they are there, we just need to prepare the queries (if
>>> needed) I could help setting up everything.
>>>
>>>
>>> http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-views-querying-rest-api.html here
>>> you can see an example, the APIs are generated automatically. I can set up
>>> the infrastracture, define the DB with someone and just make some tests :)
>>>
>>>
>>> On Tue, Mar 26, 2013 at 12:18 AM, Joshua Strobl <truthfromlies@xxxxxxxxx
>>> > wrote:
>>>
>>>> I do want to say, Goncalo, since I forgot to mention it in my prior
>>>> email, that if you could work on setting up and maintaining the
>>>> infrastructure, I can handle the API.
>>>>
>>>> You'd have my love...or a cookie. Whatever you prefer. A cookie sounds
>>>> better.
>>>>
>>>> - Joshua Strobl
>>>>
>>>
>>>
>>
>> --
>> Mailing list: https://launchpad.net/~elementary-dev-community
>> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~elementary-dev-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>>