A new critical blog discussing Seaside - now concrete proposals

> Apache is what I meant
>
> James Robertson
> Cincom Smalltalk Product Evangelist
> http://www.cincomsmalltalk.com/blog/blogView
> Talk Small and Carry a Big Class Library
>
>
>
>
> On Apr 20, 2009, at 3:44 PM, Carl Gundel wrote:
>
>> Thanks James.  When you say URL rewriting, do you mean with Apache,  
>> or is this something that is build in to the Opentalk server?
>>
>> -Carl
>>
>> On Apr 20, 2009, at 3:40 PM, James Robertson wrote:
>>
>>> Carl,
>>>
>>> You can establish shorter entry points.  I covered "static" entry  
>>> points here:
>>>
>>> http://www.cincomsmalltalk.com/userblogs/cincom/blogView?content=seaside_tutorial11
>>>
>>> I know this is covered in other Seaside tutorials; that's where I  
>>> found the info in the first place :)
>>>
>>> Additionally, using url rewriting, you can advertise any url you  
>>> want.
>>>
>>> James Robertson
>>> Cincom Smalltalk Product Evangelist
>>> http://www.cincomsmalltalk.com/blog/blogView
>>> Talk Small and Carry a Big Class Library
>>>
>>>
>>>
>>>
>>> On Apr 20, 2009, at 3:27 PM, Carl Gundel wrote:
>>>
>>>> Long URLs are ugly and my Run BASIC customers are already  
>>>> complaining about the long Seaside related URLs.  They want them  
>>>> shorter and simpler, so I'm not about to make them even longer  
>>>> than they already are.
>>>>
>>>> -Carl
>>>>
>>>> On Apr 20, 2009, at 3:14 PM, Boris Popov wrote:
>>>>
>>>>> I'm sorry, why are long URLs an issue for you?
>>>>>
>>>>> -Boris
>>>>>
>>>>> --
>>>>> +1.604.689.0322
>>>>> DeepCove Labs Ltd.
>>>>> 4th floor 595 Howe Street
>>>>> Vancouver, Canada V6C 2T5
>>>>> http://tinyurl.com/r7uw4
>>>>>
>>>>> [hidden email]
>>>>>
>>>>> CONFIDENTIALITY NOTICE
>>>>>
>>>>> This email is intended only for the persons named in the message  
>>>>> header.
>>>>> Unless otherwise indicated, it contains information that is  
>>>>> private and
>>>>> confidential. If you have received it in error, please notify  
>>>>> the sender
>>>>> and delete the entire message including any attachments.
>>>>>
>>>>> Thank you.
>>>>> -----Original Message-----
>>>>> From: [hidden email]
>>>>> [mailto:[hidden email]] On Behalf Of  
>>>>> Carl
>>>>> Gundel
>>>>> Sent: Monday, April 20, 2009 12:13 PM
>>>>> To: Seaside - general discussion
>>>>> Subject: Re: [Seaside] Swazoo, VisualWorks, and Seaside 2.8
>>>>>
>>>>> Ah, I looked at SeasideServer before but I was baffled by the  
>>>>> lack of
>>>>> instance side methods.  Everything is in the class methods.  
>>>>> Okay, so
>>>>> I look at the rootDirectory method.  It returns 'seaside'.  Is  
>>>>> this a
>>>>> disk folder?  I change it to point at my static files using the
>>>>> rootDirectory: method and now my app isn't even found.  My  
>>>>> Seaside app
>>>>> isn't a disk file, so why does this affect it?
>>>>>
>>>>> Am I supposed to use WAExternalFileLibrary for this?  It forces  
>>>>> a very
>>>>> long URL.  The class comment gives this example
>>>>> http://localhost:7777/seaside/files/external/myfile.png
>>>>>
>>>>> With the VisualWave server I can do this
>>>>> http://localhost:7777/myfile.png
>>>>>
>>>>> Or I can specify a subfolder of the public root:
>>>>>
>>>>> http://localhost:7777/special/myfile.png
>>>>>
>>>>> I realize that I can write my own WAFileLibrary subclass, but it  
>>>>> seems
>>>>> like it should be easy to do what I need out of the box.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Carl
>>>>>
>>>>> On Apr 20, 2009, at 2:18 PM, James Robertson wrote:
>>>>>
>>>>>> See class SeasideServer.
>>>>>>
>>>>>> James Robertson
>>>>>> Cincom Smalltalk Product Evangelist
>>>>>> http://www.cincomsmalltalk.com/blog/blogView
>>>>>> Talk Small and Carry a Big Class Library
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Apr 20, 2009, at 1:55 PM, Carl Gundel wrote:
>>>>>>
>>>>>>> On Apr 20, 2009, at 1:12 PM, John M McIntosh wrote:
>>>>>>>> If you check the archives there is some heated arguments  
>>>>>>>> about the
>>>>>>>> Swazoo licence history.
>>>>>>>> At this point it's LGPL, so can you live with that?
>>>>>>>
>>>>>>>
>>>>>>> I'm not quite sure if I can.  I'd really prefer to use  
>>>>>>> Opentalk if
>>>>>>> I can just figure out how to programmatically:
>>>>>>>
>>>>>>> -Get the web server for my Seaside app
>>>>>>> -Change the port number for the web server
>>>>>>> -Specify a root folder for static resources so that any URL.  
>>>>>>> For
>>>>>>> example if I specify the folder to be c:\myseasideapp\public
>>>>>>> including a file named asdf.html then the URL
>>>>> http://www.mydomain.com/asdf.html
>>>>>>> resolves to that file.  Subfolders should also work.
>>>>>>>
>>>>>>> These things are probably easy once you know how to do them,  
>>>>>>> but so
>>>>>>> far I haven't managed to figure it out.
>>>>>>>
>>>>>>> -Carl Gundel
>>>>>>> http://www.runbasic.com
>>>>>>> _______________________________________________
>>>>>>> seaside mailing list
>>>>>>> [hidden email]
>>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> seaside mailing list
>>>>>> [hidden email]
>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/ 
>>>>>> seaside
>>>>>
>>>>> _______________________________________________
>>>>> seaside mailing list
>>>>> [hidden email]
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>> _______________________________________________
>>>>> seaside mailing list
>>>>> [hidden email]
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> [hidden email]
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> 2009/4/20 Carl Gundel <[hidden email]>:
>> Apache is great, and I use it myself.  However for my market Apache  
>> is only
>> for advanced users.  I must provide a super-easy out of the box  
>> experience.
>
> Just to understand your situation better: You distribute your Seaside
> application to your clients and they run it on their machines? If so
> do they run it on their desktop machines or on their servers?
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> If a Seaside site detects a possibly hijacked session, it would be
> nice to programmatically replace their session with a new session, and
> otherwise continue.  I realize that enough information would have to
> exist in the URL so that a new session could be built pointing to the
> right point in the website, but that's not the problem for me.
>
> I'm not sure how to programmatically, and transparently, replace a
> session with a new session, so that the user doesn't otherwise even
> know that it happened.  Right now I immediately expire the session,
> and so they get the usual "session has expired" message, with the web
> app (by itself) then goes to the app entry point with a new session.
>
> How do I make this process more transparent, so that the user isn't
> even aware that the session has been switched out from under them?
>
> Nevin
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>