Re: [xwt-users] RPC/servlet session state with XWT?

LGPL is what XWT is under, thus would make it 'simpler' to explain to a 
customer that the parts are all LGPL.

The reason I asked is I would rather start from something that someone 
already has than reinvent. The advantage here is also more eyes on the 
security side, beyond just reusable code. For example review for man in 
the middle and other security attacks. Now that the licensing is simpler 
I think this should be a really good start for a generic & reusable 
[java servlet] login system.

-Jeff

Emiliano Heyns wrote:

>On Fri, Sep 19, 2003 at 08:28:44PM -0500, Jeff Buhrt wrote:
>
>  
>
>>Why the Affero GPL license?
>>    
>>
>
>Ah, because the splitting off of this code is a work in progress, and
>I hadn't got to the licensing itself yet. I was thinking either LGPL or
>BSD for this portion of the code but had wanted to discuss that on this
>list.
>
>  
>
>>Is the only intent section to change section 2d? (basically all users 
>>can request copies, vs just the provider)
>>    
>>
>
>That will be the case for the rest of the code but not this code.
>
>  
>
>>I assume the intent is to be GPL vs LGPL?
>>LGPL would be ok for my customer, but a more restrictive modified GPL of 
>>the login/sessioning itself  might be an issue.
>>
>>Comment? Thoughts?
>>    
>>
>
>Screw it, this code ain't rocket science. The only 'clever' bit is that
>it makes use of the XWTs built-in Digest handling so it'll be the fastest way
>to do it. I'll recast to BSD unless someone makes a compelling case for
>LGPL.
>
>  
>