Hello,
Does mochikit's xml-rpc code support session validation?
I'm writing some code using cherrypy, and I want to use Mochikit to
access the data, I need it to send the cookies about the session ID or
something like that, so the method called in cherrypy knows which
session data to use.
var res =
MochiKit.Async.doSimpleXMLHttpRequest(this.link,formContents('loginform'));
If it's your code, it's normal it doesn't work, or I don't know what's
this.link : formContents is a function of MochiKit.DOM, not a slot of
nodes.
If it's not your code, please post your real code.
--
Thomas,
Thank you for the notes. I've made a few changes to the API I hope
you'll like:
1. I now return a MochiKit.Signal.Event object instead of mangling
the native event object. (The native event object is available as the
theParam.event property.)
2. I've changed the name of the
On Jan 23, 2006, at 10:12 AM, Thomas Hervé wrote:
var res = MochiKit.Async.doSimpleXMLHttpRequest
(this.link,formContents('loginform'));
If it's your code, it's normal it doesn't work, or I don't know what's
this.link : formContents is a function of MochiKit.DOM, not a slot of
nodes.
If
I think !== and === instead of cne and ce may work.
On 23-Jan-06, at 11:15 AM, Jonathan Gardner wrote:
My concern is that slots will get called twice. This is really bad
if you are
connecting a toggle type slot to a signal. You'd expect pressing
the button
to call it exactly once, but
XMLHttpRequest does not work cross-domain.
-bob
On Jan 23, 2006, at 11:48 AM, Ricardo de Oliveira Saldanha wrote:
I made a workaround (function convert), but the function
MochiKit.DOM.formContents isn´t working for me.
Another thing I have noticed is that if I call this page from
firefox
On Jan 23, 2006, at 7:52 AM, Saldanha wrote:
I think that formContents may be not working ...
Don't use a name attribute for your form tag. If you drop the name,
then it works. Right now it thinks that elements that have a name
attribute are part of the form.
-bob
I agree that modifying the event object is undesirable, however, I
think there is a strong case to add standard w3c event methods if
missing (IE, Safari 2) such as event.preventDefault.
so that you could use
...connect(myElement, onclick, function(e){e.preventDefault()});
without thinking
On Jan 23, 2006, at 3:54 PM, Eoghan wrote:
I agree that modifying the event object is undesirable, however, I
think there is a strong case to add standard w3c event methods if
missing (IE, Safari 2) such as event.preventDefault.
so that you could use
...connect(myElement, onclick,
