On Sun, Sep 11, 2011 at 2:14 AM, Stephan Beal wrote:
> Hi, all,
>
> Is there a real semantic difference between fossil_panic() and
> fossil_fatal()? The only logic diff i see is that fossil_panic() only
> outputs once when in CGI mode, but fossil_fatal() can potentially output
> more than once (v
On Sep 9, 2011, at 7:35 PM, Stephan Beal wrote:
> On Fri, Sep 9, 2011 at 7:04 PM, Twylite wrote:
>
>> e.g. "/timeline" produces HTML by default, but "/timeline.json" would
>> return the same information in JSON.
>>
>
> i like that idea. i hadn't thought of simply using an extension. i don't
>
Unfortunately I need to parse this information programatically (and
fast), so putting fossil into ui mode, hitting the url, and parsing the
html will take too long.
Thanks for the suggestion though. If only the 'timeline' command could
display parents, or if 'info' could take -R...
-Jeff
On 9/1
On Sun, Sep 11, 2011 at 3:50 PM, Weber, Martin S wrote:
> Right now for the fossil repository itself, I can read & write some stuff,
> but I cannot read everything. For example, I cannot read the complete list
> of users.
You're right. The only multi-user repo i work on is fossil's, so i was
ign
Right now for the fossil repository itself, I can read & write some stuff, but
I cannot read everything. For example, I cannot read the complete list of
users. So the sentence "As far as i can see so far, the only ops which _need_
to be authenticated (for purposes of a JSON interface) are write-
You could probably do it through the UI. fossil ui repo.fossil and then just
use the checkin id, I don't know the exact url you can use, but between the
visual timeline and the /info/ url, you can probably get the info you need.
Tomek
On Sat, Sep 10, 2011 at 3:30 PM, Jeff Slutter wrote:
> (Via
On Sun, Sep 11, 2011 at 10:00 AM, Ben Summers wrote:
> Private repositories will need the user to authenticate to get read only
> access.
>
Doh, i completely didn't think of that. You're right.
> I trust you're planning to respect the permissions for the anonymous user?
>
>
i am now!
--
On 11 Sep 2011, at 05:55, Stephan Beal wrote:
>
> In a JSON context, link-following is not an issue. There are no links, as
> such, in JSON docs - though individual JSON strings might incidentally
> contain HTML link strings, bots don't generically try to extract HTML text
> from JSON. Doing a
8 matches
Mail list logo
