Hi
Although the Hunchentoot documentation says "... the internal structure of SESSION objects should be considered opaque ..." and the functionality of session-id and session-start can be trivially implemented, I am wondering if these two readers can be exported?
session-start is useful for seeing how long users have been on the system. session-id is useful for session identity. Why re-implement them when Hunchentoot already has the functionality?
Regards. Nico
On Thu, Sep 23, 2010 at 14:57, Nico de Jager ndj@bitart.cc wrote:
Although the Hunchentoot documentation says "... the internal structure of SESSION objects should be considered opaque ..." and the functionality of session-id and session-start can be trivially implemented, I am wondering if these two readers can be exported?
session-start is useful for seeing how long users have been on the system. session-id is useful for session identity. Why re-implement them when Hunchentoot already has the functionality?
I am not opposed - Send a patch for review (http://weitz.de/patches.html).
-Hans
Hans Hübner hans.huebner@gmail.com writes:
On Thu, Sep 23, 2010 at 14:57, Nico de Jager ndj@bitart.cc wrote:
Although the Hunchentoot documentation says "... the internal structure of SESSION objects should be considered opaque ..." and the functionality of session-id and session-start can be trivially implemented, I am wondering if these two readers can be exported?
session-start is useful for seeing how long users have been on the system. session-id is useful for session identity. Why re-implement them when Hunchentoot already has the functionality?
I am not opposed - Send a patch for review (http://weitz.de/patches.html).
Ok, thanks - no problem. I feel stupid asking this, but how do I get the svn version of Hunchentoot:
$ svn co http://bknr.net/trac/browser/trunk/thirdparty/hunchentoot svn: XML data was not well-formed
Also, do I have to update that ugly doc/index.xml file in a text editor, are there some kind of tool to edit it, or do you generate (parts of) it from the source code?
On Fri, Sep 24, 2010 at 10:47, Nico de Jager ndj@bitart.cc wrote:
Ok, thanks - no problem. I feel stupid asking this, but how do I get the svn version of Hunchentoot:
$ svn co http://bknr.net/trac/browser/trunk/thirdparty/hunchentoot svn: XML data was not well-formed
svn co http://bknr.net/svn/ediware
will get you the whole ediware tree, which includes matching development versions for Hunchentoot and its dependencies.
Also, do I have to update that ugly doc/index.xml file in a text editor, are there some kind of tool to edit it, or do you generate (parts of) it from the source code?
It is an XML file, you can use any editor to edit it. It is the master copy of the documentation. There are tools that we used to extract the docstrings into the XML documentation, but they are not readily deployable. I'd suggest that you add the docstrings and then copy them to the XML file manually.
Please make sure that it is still well formed after you've modified it (xmllint can help with that). Emacs 23 includes the nXML mode, which validates well-formedness on the fly.
-Hans
Hans Hübner hans.huebner@gmail.com writes:
On Fri, Sep 24, 2010 at 10:47, Nico de Jager ndj@bitart.cc wrote:
Ok, thanks - no problem. I feel stupid asking this, but how do I get the svn version of Hunchentoot:
$ svn co http://bknr.net/trac/browser/trunk/thirdparty/hunchentoot svn: XML data was not well-formed
svn co http://bknr.net/svn/ediware
will get you the whole ediware tree, which includes matching development versions for Hunchentoot and its dependencies.
Also, do I have to update that ugly doc/index.xml file in a text editor, are there some kind of tool to edit it, or do you generate (parts of) it from the source code?
It is an XML file, you can use any editor to edit it. It is the master copy of the documentation. There are tools that we used to extract the docstrings into the XML documentation, but they are not readily deployable. I'd suggest that you add the docstrings and then copy them to the XML file manually.
Please make sure that it is still well formed after you've modified it (xmllint can help with that). Emacs 23 includes the nXML mode, which validates well-formedness on the fly.
Attached, please find the patch. I added the new documentation at the end of the "Sessions" section, but will be disappointed if Edi don't make me rearrange it somehow :-)
Almost forgot this one. Also in SVN now.
Thanks, Edi.
On Sat, Sep 25, 2010 at 3:31 PM, Nico de Jager ndj@bitart.cc wrote:
Hans Hübner hans.huebner@gmail.com writes:
On Fri, Sep 24, 2010 at 10:47, Nico de Jager ndj@bitart.cc wrote:
Ok, thanks - no problem. I feel stupid asking this, but how do I get the svn version of Hunchentoot:
$ svn co http://bknr.net/trac/browser/trunk/thirdparty/hunchentoot svn: XML data was not well-formed
svn co http://bknr.net/svn/ediware
will get you the whole ediware tree, which includes matching development versions for Hunchentoot and its dependencies.
Also, do I have to update that ugly doc/index.xml file in a text editor, are there some kind of tool to edit it, or do you generate (parts of) it from the source code?
It is an XML file, you can use any editor to edit it. It is the master copy of the documentation. There are tools that we used to extract the docstrings into the XML documentation, but they are not readily deployable. I'd suggest that you add the docstrings and then copy them to the XML file manually.
Please make sure that it is still well formed after you've modified it (xmllint can help with that). Emacs 23 includes the nXML mode, which validates well-formedness on the fly.
Attached, please find the patch. I added the new documentation at the end of the "Sessions" section, but will be disappointed if Edi don't make me rearrange it somehow :-)
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
-
Edi Weitz -
Hans Hübner -
Nico de Jager