On Fri, 26 Oct 2012 23:00:41 -0200, Geoff Callender
<[email protected]> wrote:
I can't find a definition of SPI in this mailing list. Is it:
Yep, it doesn't seem to me that everyone talking about SPIs and
abstraction layers have a different definition for them. Howard, as you're
the one who started this discussion, how would you define them?
- Service Provider Interface?
- Script Programming Interface?
- Single Page Interface?
I'm guessing it's #2.
I guess it's #1, but #2 is maybe the same thing. :)
If so, then it sounds like an excellent idea, and I'm guessing it would
have to be written in raw, vanilla javascript (the lowest common
denominator)
I agree with this part.
so that everyone can call it from their preferred flavour of javascript.
But not with this one. People (a.k.a. not Tapestry itself) would use their
preferred JavaScript frameworks directly, while Tapestry itself would use
the SPI in order to not use Prototype or jQuery directly. This way, the
Tapestry JavaScript code would be 100% JS framework-agnostic.
If I'm on track now, could someone post some examples/proposals of
interface code, eg. the interface for Zone handling; so we can see what
we're talking about?
+1.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
