GnuCash as server [WAS: Re: GnuCash page on GO site]

[Clayton Carter]

> | PS - as for the question of how to make evo act on a SX, what's wrong
> | w/ 'PUT /scheduled?SXid=00000?action=enter' ?  
> 
> PUT is already the verb in there.  If you're going to have the "action"
> part, then "PUT" just becomes "DO", which isn't really useful.

	Right, OK, so PUT is wrong.  But I guess, for my example, GET
would work just as well.  Just some way of telling GC what needs to be
done.  You wouldn't care about the return, per se.

> The gnucash/scheduled-transaction typed data would have to contain enough
> information for Evo to be in a position to do a GET,PUT,POST or DELETE
> something...  Don't quite know what that is, yet.  Probably the only real
> thing to do is open GnuCash, or get the next-level of detail for display.

	You folks know way more about this than I do, but I have it in
mind that Evo (or whatever) wouldn't need MUCH information.  Just a
date and a transaction ID.  Then you could either `open' GC to the
specific transaction, or just right click and say `enter', to which
evo would do a POST or GET or whatever to tell GC (through HTTP) to go
ahead and OK that transaction.  When an SX comes up for me, all I have
to do is punch the OK button and it's all taken care of.  Why should
this be any different?  Instead of pressing one button for an SX,
you're issuing one `command' for an SX.

	Actually, I should just be quiet here since I have something
very specific and minimalist in mind and I'm sure you all have
something more expansive.  Anyway, my concerns have been voiced and,
in fact, already addressed.

Clayton