Re: [Tclhttpd-users] Sanity check..

[Nicolas B. <ni...@ma...>]

Colin McCormack wrote:

>On Thu, 2004-10-07 at 19:14, Nicolas Boretos wrote:
>
>  
>
>>As much as I 
>>understand, "tclhttpd" is my "single user", and that
>>read/writes are sequential/serialized, the equivalent of opening a 
>>console and playing with the mk db...
>>    
>>
>
>That's a good way to look at it.
>  
>
So, does this mean you feel that I should not have concurrency issues w/ 
th mk?

>  
>
>>We are running single threaded tclkit, with the stripped down 
>>tclhttpdmin.kit for the web-server, on a debian3 box
>>    
>>
>
>Debian and tclhttpd?  You are clearly a man of discretion and good
>taste. :)
>
>  
>
>>A few key points about the app.
>>1. A .tclaccess file permits access to the db
>>    
>>
>
>Wrong place.  Should be a .tml file (just dir/.tml is sourced in.)
>  
>
I'm not sure I get it;-(...The .tclaccess file  calls the browsers login 
stuff...I'm not sure that a .tml file is designed for this
Or, am I mis-understanding you...

>  
>
>>2. From then on,  ncgi package is used for user_id and all form variables
>>3. The whole app uses self-posting .tml pages, with Doc_Redirects to the 
>>next page...
>>    
>>
>
>I like this approach, I like .tml pages.
>  
>
I do too..

>Handling state through Redirects is a pain though.  Perhaps we should
>come up with a nicer abstraction to cover the messy details of building
>systems of DFSAs to represent interactions via templates.
>  
>
Great idea!...Errr, WTF is a DFSA?
I have really gotten burned redirects and form variables with it this 
time...
This project kinda went like this...
Are you sure you dont want a desktop app? No, it's a really simple app 
they say, and the Web is good ;-)
We started with simple entry (submits)---o.k
Then "they" wanted to edit the stuff.. So now we had to populate the 
pages w/ data read.(now we have logics like new record? old record? etc..)
We also had to read and overwrite the db with the edits.....
Then they wanted "sessions within a page", good case for mk's nested 
views here...but correctly populating the pages w/ db reads became a chore..
Then they wanted to query the db, see all records, but be able to edit 
only their own data....
And now they want to distribute the app at some point read-only ('bout 
my only saving grace here... tclhttpd-startkit anyone?

>One facility you should become familiar with is [Httpd_Suspend] and
>[Httpd_Resume], which allows you to leave the connection open (for some
>period) while processing other incoming connections.  It might be useful
>in this application.
>  
>
I think in this case I would probably want the opposite; meaning I want 
to complete my current mk transaction before moving on
to the next...

regards,

nicolas