Sorry Slava, try the same repo again:
g...@github.com:addrummond/factor.git
Alex
On 23 February 2010 02:43, Slava Pestov wrote:
> On Tue, Feb 23, 2010 at 5:25 PM, Alex Drummond
> wrote:
>> I'm a bit of a git newbie, so let me know if you'd rather I pushed the
>> changes some other way.
>
> Hi
On Tue, Feb 23, 2010 at 5:25 PM, Alex Drummond
wrote:
> I'm a bit of a git newbie, so let me know if you'd rather I pushed the
> changes some other way.
Hi Alex,
You might want to create your repository again. You removed the work
folder, added work.zip, and removed a file from io.encodings.japa
On Tue, Feb 23, 2010 at 5:25 PM, Alex Drummond
wrote:
> Currently, there is nothing to stop a user editing their profile such
> that they end up with the same registered email address as another
> user. Eventually, I may try extending the auth protocol a bit to allow
> errors of this sort to perco
Hi Slava,
I've written some docs for the couchdb auth implementation and put it
up here (in master):
g...@github.com:addrummond/factor.git
I'm a bit of a git newbie, so let me know if you'd rather I pushed the
changes some other way.
Currently, there is nothing to stop a user editing their prof
On Sun, Feb 21, 2010 at 10:53 PM, Alex Drummond
wrote:
> What's the best way for me to
> send it to you?
Set up a github account.
> I'll probably take a look at furnace.sessions at some point. Right now
> I am just using sqlite for sessions. In fact, this *probably* makes
> more sense than using
Sure, I think the auth implementation is pretty much done now. I guess
I should test it for a few days first. What's the best way for me to
send it to you?
I'll probably take a look at furnace.sessions at some point. Right now
I am just using sqlite for sessions. In fact, this *probably* makes
mor
Excellent. Looking forward you seeing your code contributed.
Are you interested in refactoring furnace.sessions to allow alternate
session storage as well? Right now its hard-coded to use the database,
but it could also use in-memory sessions (faster performance, no
failover) or couchdb (for peopl
Oops, when I switched back to using allow-edit-profile instead of the
hack in the previous email, it worked fine.
I guess there must previously have been a bug in my update-user method
which somehow led me to think that it wasn't being called at all. (I
am just using , so there wouldn't have been
Hi Alex,
Does the call-responder* method of your authentication realm execute
call-next-method? Because M: realm call-responder* calls
save-user-after, which sets up a destructor that will call update-user
when the request is done. If you implement the update-user generic
word then editing the pro
Hi,
I've written an implementation of the furnace authentication provider
protocol for couchdb. I decided to do a direct implementation, rather
than write a tuple db interface for couchdb, since when using couchdb
you need to jump through various hoops in order to ensure the
uniqueness of username
10 matches
Mail list logo
