> I thought it was obvious that session-name-string-pair kept track of
> hunchentoot sessions, and was one part of a two step mapping to
> actions (the other being the action-code returned through function-or-
> action->action).
>
> But I have to ask: where is weblocks:session-name-string-pair supposed
> to be used? After looking at the source to all my pages, I see that
> the second param (sessionstring) in all the calls to initiateAction is
> always blank! Which in turn implies that the session-name-string-pair
> fn always returns nil.

It would have helped to look at the source for this function. :)

This value is only needed in this case:

  (and *rewrite-for-session-urls*
       (null (cookie-in *session-cookie-name*))
       (hunchentoot::session-cookie-value))


> The code I'm using (the url gets sent on to flash, which, which, as
> seen the backtrace, does get to communicate with hunchentoot)
>
> (defun file-upload-receiver (&rest args)
>   "A function called when a file is received. Writes to debug so we
> can see what up yo."
>   (break "handler called") ;never gets here.
>   (save-debug-info "Foto File saved name: ~{ ~A ±± ~} " args)
>   (setf (setf (hunchentoot:return-code) hunchentoot:+http-ok+))
>
> ;Result of this is the url I'm using
> (defun make-receiver-shiznit (func &rest args)
>   (let* ((actioncode   (weblocks::function-or-action->action (lambda
> (&rest args) (funcall func args))))
>        (sessionid    (weblocks::session-name-string-pair))
>        (url          (format nil "/?~A&action=~A&pure=true" sessionid
> actioncode)))

^^^ don't do this, there's MAKE-ACTION-URL that takes care of this.

I'm going to check this out...

  Leslie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to