incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Pollak <feeder.of.the.be...@gmail.com>
Subject Re: [HELP] is old REST API broken ! Showstopper!
Date Fri, 20 Nov 2009 16:10:52 GMT
On Fri, Nov 20, 2009 at 5:04 AM, Richard Hirsch <hirsch.dick@gmail.com>wrote:

> OK. It appears to be working again but maybe still do can some tests
> on the REST API. I don't trust it yet....
>

The worst ever bug crept into Lift a few days back.  Sessions were getting
destroyed.  That's fixed now.


>
> I think one of problems is that there is currently a conflict for
> current Twitter clients which can use laconica (such as twhirl) expect
> the "/api" prefix to access systems that support the twitter API.
> Currently "api" is being used by our REST API.  So, there is a
> conflict. Right now, the default in ESME for the twitter api is
> "/twitter" which means that most existing twitter clients won't work
> for ESME access.  I previously had set the default twitter prefix to
> "api" which allowed the twitter clients to work but broke our REST
> API.
>
> Ideally, we might change the prefix for our API to "esmeapi" in order
> to avoid conflicts with existing apis.
>
> Thoughts?
>
> D.
>
> On Fri, Nov 20, 2009 at 1:40 PM, Vassil Dichev <vdichev@apache.org> wrote:
> >> What is strange is that the old Air client works.
> >
> > So did Twitter clients last time I tried. If you provide a user, it
> > will use that, but for Twitter API at least, any password would work.
> >
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message