Re: [WWdevel] more logging

[Michael G. <ga...@ma...>]

>
> Since part of the rationale for the transaction log is to back up  
> the sql database, keeping it as a file makes sense.  But, it should  
> probably be merged with the answer log (with maybe the tiny extra  
> bit of information of logging submit/check/preview :) ).
>
>

Hi John,

I'm not sure that we've ever used the transaction log to rebuild a  
database -- the information is there, but not in a very useable form.
The sql databases have their own efficient methods for dumping a  
backup image, or even of journalling every transaction if that is
desirable.  I want to to shift the burden of backup and efficiency to  
those software projects.  They have a lot more manpower. :-)

Thanks for adding the journalling facility to the current WeBWorK2.   
It is quite useful for trouble shooting problems after the fact.

>> On a separate note I think we would be interested in the changes   
>> needed to accommodate the ASU login and authentication scheme.  We  
>> haven't had much experience with this yet but if it's  possible  
>> I'd like to factor things so that ContentGenerator.pm would be  
>> fixed  and Authen.pm and/or if necessary Login.pm could be   
>> subclassed to allow for a variety of authentication schemes.
>>
>
> Some things would probably be easy, and others much harder.  The  
> main changes to ContentGenerator relate to logout.  We have to show  
> a particular icon for logout, and it has to call a particular  
> university url.  So, I removed the logout link from the left panel  
> and replaced the link in the upper-right corner with the icon  
> linking to the university url instead of calling the logout  
> module.  I tinkered with the logout module, but this meant that I  
> had one fewer module to change.  So, I leave it as is, and it never  
> gets called.  I think I could have done the icon through the  
> template, but then I would still need to remove the webwork logout  
> link in the upper right corner.
>
> I changed Login.pm so the only options are to log in through the  
> university, or to guest login.
>
> I changed Options.pm since webwork has no access to actual  
> passwords.  The standard message was potentially confusing since  
> university passwords could be changed, just not through webwork.   
> If you wanted to make that configurable, I imagine it could be a  
> string to show when password changes are not allowed, and set in  
> Constants.
>
> The biggest changes were to Authen since that's where we need to  
> deal with the university system for login-redirect and reading  
> their cookie.  I think there was something done in webwork to make  
> that easier, but I haven't looked at it.
>
> There are a few things which could be better when it comes to  
> practice users, but they haven't caused any problems.
>
> You can see the result by logging into any of the ASU courses.  Of  
> course, the login through ASU button will just get you the ASU  
> login page where you will be stuck.  But, you can login as a guest  
> and everything looks the same as if you were a registered student.
>
> John

Thanks, John.  Once the beginning of semester flurry dies down I'd  
like to look a the changes you've made in your modules and
also at the experience of others who have been using university  
authentication of one form or another.  We'll see what improvements
can be made in the way the current code is factored.
>
>
>