[Seaside] Authentication task and https

[Ramon Leon]

> 
> Julian,
> 
> Are there any restrictions on how or on which classes to set the
> protocol option?  So far, I have used #registerAsApplication: and then
> set preferences.  But unless I am missing something, I can't simply
> browse for implementers of #serverProtocol:.  Is there a way to set a
> protocol for something that does not deserve the label of 
> "application"
> (which I read as entry point to Seaside)?  As an example, 
> suppose I have
> a task to get a file name, ask for some text, perhaps present 
> a form to
> edit it, and then #answer: a result of the interaction; how would I go
> about setting its server protocol without creating an entry point?
> 
> Bill

See http://code.google.com/p/seaside/issues/detail?id=97

I think that's what you're looking for.

Ramon Leon
http://onsmalltalk.com