[Citadel Development] Re: Latest SVN + CygWin

2008-05-21 Thread wduchene
We will convert them! And we can make it easy for them to love it with a
slick installer as well!

 
>Wed May 21 2008 10:57:43 PM EDT from IGnatius T [EMAIL PROTECTED] 
>Subject: Re: Latest SVN + CygWin
>
>Very happy to hear that it's working on Cygwin now.  Soon, even the great
>unwashed masses of Windows users will be flocking to the Citadel revolution!!
>   
>   
> Seriously though, we should get together sometime to sync up on a
>"vision" for the Citadel system.  It's been a while since we've done that. 
> I'd love it if this could happen in meatspace, but since we're all over the
>world I guess an online meeting will have to suffice.  
>

[Citadel Development] Citadel commit log: revision 6306

2008-05-21 Thread ajc

r6306 | ajc | 2008-05-21 22:58:14 -0400 (Wed, 21 May 2008) | 1 line
Changed paths:
   M /trunk/citadel/modules/openid/serv_openid_rp.c

more openid 1.1 hacks



[Citadel Development] Re: Latest SVN + CygWin

2008-05-21 Thread IGnatius T Foobar
Very happy to hear that it's working on Cygwin now.  Soon, even the great 
unwashed masses of Windows users will be flocking to the Citadel 
revolution!!
   
 Seriously though, we should get together sometime to sync up on a 
"vision" for the Citadel system.  It's been a while since we've done that. 
 I'd love it if this could happen in meatspace, but since we're all over 
the world I guess an online meeting will have to suffice.  
  


[Citadel Development] Latest SVN + CygWin

2008-05-21 Thread wduchene
Wow! It looks like the bug that was preventing the latest version of webcit
from working correctly has been fixed. I was able to perform the build
successfully. I don't know if it gets said very often, but you guys do know
that your all AWESOME right? I'll keep testing it out to see if I find
anything...

[Citadel Development] Citadel commit log: revision 6305

2008-05-21 Thread ajc

r6305 | ajc | 2008-05-21 17:43:26 -0400 (Wed, 21 May 2008) | 3 lines
Changed paths:
   M /trunk/citadel/configure.ac
   M /trunk/citadel/control.c
   M /trunk/citadel/modules/openid/serv_openid_rp.c
   M /trunk/citadel/modules/rssclient/serv_rssclient.c
   M /trunk/citadel/server_main.c

* More work on OpenID 1.1 Relying Party support
* Changed the startup order to put the citadel.control lock check happen 
*before* the databases
  are opened.  Otherwise it can corrupt the databases before the lock check 
shuts it down.



[Citadel Development] Re:ECC

2008-05-21 Thread Bryon Roche
About ECC:

Of course I'm not implementing it directly!  That would be silly, and code
duplication, to boot.

As for patent liability, yeah, that would fall on whomever distributes
software that links to openssl.  Since citadel is dynamically linked, that
mean's you're not distributing openSSL libs yourself. (are you? I only track
SVN and .debs I build from it, I don't know what's included in the easy
install package for example)

[Citadel Development] ECC

2008-05-21 Thread IGnatius T Foobar
   
 Regarding ECC crypto ...  
   
 You're not actually including portions of an ECC implementation in 
Citadel, are you?  You're just enabling those functions if they are 
present in OpenSSL.  Unless I am misunderstanding?  
   
 In that case it would seem that the burden of unencumbrance falls upon 
OpenSSL, not Citadel, even if we allow that particular code to run.  
   
 Maybe I don't understand the issue.  
  


[Citadel Development] (no subject)

2008-05-21 Thread IGnatius T Foobar
 >*  we don't minify our JS; since  JSMin is available under the BSD 
license   
 >(http://crockford.com/javascript/jsmin) should we add it to webcits make 
  
 >install process (we don't need to distribute it... ) and compress our   
 >javascript files while installing?   
   
 We could probably save a few cycles by minifying our JavaScript, but I'm 
not sure where to do it.  I wonder if it would make sense to do it as part 
of the bootstrap process?  It really would make life difficult for us 
developers though.  
   
 Most of our JavaScript calls are where they need to be ... we can't move 
them to the end of the page because we don't always know where the end of 
the page is going to be ... there are a lot of conditionals.  
   
 Expires headers are easy.  All you have to do is go into webcit.c and 
locate the function called http_transmit_thing().  Oops ... ok, looks like 
I already did that.  Instead, you want to look in the function called 
output_headers().  You'll see that if 'cache' is nonzero, we allow the 
browser to cache the page.  For that, you'll see that if the page is 
cacheable we send a "Cache-control:" header.   
   
 So if you want to do an "Expires:" header as well, all you have to do is 
calculate a timestamp that's 24 hours for now, convert it to a string 
using http_datestring(), and output it in that function.  
  


[Citadel Development] Citadel commit log: revision 6304

2008-05-21 Thread ajc

r6304 | ajc | 2008-05-21 13:24:41 -0400 (Wed, 21 May 2008) | 5 lines
Changed paths:
   M /trunk/libcitadel/lib/libcitadel.h
   M /trunk/libcitadel/lib/mime_parser.c
   M /trunk/libcitadel/lib/tools.c

* Commented out the 'PrintFlat' and 'PrintFile' functions
  because they are only used in debug tests that are also commented
  out.  Silences a compiler warning.
* Removed parse_url() from libcitadel.  No longer necessary because
  libcurl handles all this stuff for us now.



[Citadel Development] (no subject)

2008-05-21 Thread dothebart
participation is allways welcome (if you can give a helping hand with
kerberos, i'm stuck there... *HINTHINT*), but if one has a look at

 http://en.wikipedia.org/wiki/ECC_patents

it doesn't seem to be that easy...

can you give statements under which conditions openssl accepted this patch? 

I'd say it needs to be turn on/off-able by configure, so if we don't get into
troubles here.

as freetype for example covers apple patents, but it seems to be ok to
distribute it...