There was also another spec which dealt in this sort of stuff which
slightly
preceded yours:
http://www.jabber.org/jeps/jep-0070.html
Yes I know
It might even work better for this sort of simple web commenting thing.
But
actually I wonder why a new JEP was created instead of adding new use
cases
to the existing one. I guess it doesn't matter though, since they were
both
deferred in the end anyway...
The thing is they work in fundamentally different ways and simply adding use
cases will not allow JEP-0070 work in the way JEP-0101 does, JEP-0070
requires that the web server be tied to a jabber server for it to work which
creates some serious scalability and security concerns which are especially
problematic for web farms, whereas JEP-0101 allows the jabber (ticket
serving) component to be completely separated from the webserver. JEP-0101
also potensially means less network roundtrips in the jabber layer as the
client can use the same ticket across multiple websites and pages without
having to re-request it, overall JEP-0101 is a much more scalable and
efficient solution.
Richard
_______________________________________________
jdev mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/jdev
