On Fri, Aug 22, 2008 at 12:01:53AM +0200, Roan Kattouw wrote:
> Jay R. Ashworth schreef:
> > On Wed, Aug 20, 2008 at 10:20:44PM +0200, Roan Kattouw wrote:
> >> Simetrical is right here: the UI and the API call the same functions,
> >> and display the results in different ways. That's exactly why there's no
> >> sense in migrating the front end to the API (and that's just forgetting
> >> about the HTTP overhead involved).
> >
> > Um, we mean different things by "API", clearly.
> >
> > What I think *you* mean by it is "a thin wrapper over the *actual* API".
> >
> > Am I wrong?
>
> In MediaWiki speak, the API is api.php . You're probably referring to
> the backend functions which *are* used by the UI.
>
> Just to clarify again: the API and the UI call *the same functions*, but
> present the results differently. That's why there's *nothing to gain
> whatsoever* in letting the UI call the API.
If api.php exposes every and only the interfaces already used by the
core code, and the current UI can't cheat and do things api.php does
not expose to the core's state, then yes, my desire and concerns are
satisfied.
Cheers,
-- jra
--
Jay R. Ashworth Baylink
jra@...
Designer The Things I Think RFC 2100
Ashworth & Associates
http://baylink.pitas.com '87 e24
St Petersburg FL USA
http://photo.imageinc.us +1 727 647 1274
Those who cast the vote decide nothing.
Those who count the vote decide everything.
-- (Josef Stalin)
_______________________________________________
Wikitech-l mailing list
Wikitech-l@...
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
