[Seaside] Questions about seaside and pharo

[Ramon Leon]

On 06/14/2018 07:39 AM, Blake McBride wrote:
> Old web architectures that made a lot of sense then aren't really 
> applicable anymore.

They'll always be applicable; the wheel of smart client dumb client will 
never stop turning.  Server based page rendering isn't outdated, it's 
not an either or situation, it's an and situation.  React and Angular 
have not replaced server rendering and Ajax updates of fragments, 
they're merely additional options you now have.  Perfectly fine and 
functional applications can and are still being done in what you call 
the old way and they always will be.

Give it a few years, the wheel will turn again and dumb clients will 
come back into fashion as they always do and have since the green screen 
mainframe days.


 > 1.  Does Pharo support multiple OS/native threads?

No.  What you do is run multiple processes on the backend and load 
balance between them via a proxy. Apache/haproxy, whatever.

 > 2.  Can I run Seaside headless?

Of course.

 > 3.  The Seaside book at 
http://book.seaside.st/book/advanced/restful/nutshell talks about REST 
services in two models but seems to only give an example for the case I 
am not interested in.  Is there a tutorial for the REST centric core model?

Frankly I wouldn't use Seaside if I were attempting RESTful services, 
I'd find another option.  There's probably already a nice Smalltalk REST 
framework, but if not it wouldn't take much effort to hack up something 
like Sinatra in Smalltalk for doing it.

-- 
Ramon Leon