Seaside (software)

Although subsequent improvement of state handling in web browser JavaScript engines have meant this aspect is less important today, Seaside's method of handling of browser state (via continuations) was an initial point of interest in the first years following its 2002 release. This mechanism provides for rollback and resumption, resolving many common issues then occurring with running web applications, adequately sustaining the state on the server-side even when the web browser's 'back' and 'forward' or 'refresh' buttons are used. Continuation based servers give the developer the ability to maintain state on the server in a scalable manner. A distinctive feature of Seaside is its integrated development environment, providing access to development tools and debugging support within an application. In development-mode, unhandled errors are reported to the web page; developers can access and alter the program code and state directly from the web page, allowing bug identifying and fixing processes to occur within an integrated development environment (IDE). A Seaside application is a set of interacting components. Each one stores state across page views and can render itself to the HTML stream. Thus, it is straightforward to write a component once and then reuse it elsewhere in an application. Seaside also supports the notion of tasks, which allow a programmer to describe the high-level logic of component interaction. Seaside is not template-oriented, and does not offer generating or using HTML templates; HTML markup is generated programmatically. (The Seaside-based Pier content-management framework does offer wiki-markup syntax for templating.) Seaside uses callbacks on closures to specify actions to be taken when clicking on a link or submitting a form. The developers and users of Seaside argue that this helps enforce separation of structure (markup) from content and presentation (Cascading Style Sheets (CSS)). Seaside's combination of components, callbacks, and closures can significantly reduce the semantic gap between a complex workflow and its representation in code. Seaside supports Ajax through integration with script.aculo.us and jQuery. Seaside also supports Comet-style server-push technology. Seaside can work with either Smalltalk-based web server implementations or other non-Smalltalk ones (Nginx, Apache). ==Philosophy==

Over the last few years, some best practices have come to be widely accepted in the web development field: • Share as little state as possible. • Use clean, carefully chosen, and meaningful URLs. • Use templates to separate the model from the presentation. Seaside deliberately breaks all of these rules. Avi Bryant, then of Dabble DB, in 2006 described it as a 'heretical' framework, arguing that this careful and reasoned rejection of the conventional wisdoms of web development led to a very effective model for developing web applications. ==Ports==

The main development of Seaside is implemented in Pharo Smalltalk. Ports for other Smalltalk dialects exist. The original development of Seaside was done on Squeak in the early 2000s. Michel Bany implemented ports to VisualWorks through Seaside version 2.7; Cincom Systems supports Seaside as part of VisualWorks as of early 2008. Instantiations announced Seaside support in its VAST (VA Smalltalk) Platform version 8.0 in 2009. The VAST Platform has continued to support Seaside through its latest version. Esteban Maringolo maintained the 2.8 port, plus some other add-ons (such as script.aculo.us) for Dolphin Smalltalk X6. Gemstone Systems implemented a port to Gemstone/S. A port of 2.8 was completed for GemStone, and a preliminary version of 3.0 runs on GNU Smalltalk 3.0a and later. The web server package in the standard library of Racket (Programming language) uses a very similar philosophy, also based on continuations. ==Criticisms==

• Compared to other web frameworks, Seaside is memory intensive. One session could accumulate several hundred kilobytes of RAM. A later release, version 2.8, significantly reduces this size (e.g., a formerly typical 200 KB size becomes 50 KB). • Seaside does not follow representational state transfer (REST) by default. Instead, Uniform Resource Locators (URLs) hold session key information, and meaningful URLs must be generated explicitly. ==Open-source projects using it==

Many open-source projects use Seaside, some of which are: • Magritte – a meta-description framework with a tight integration into Seaside • Pier – a content management system and high level application framework for Seaside • ADK Project ==Proprietary projects using it==

Many proprietary projects use Seaside, some of which are: • Dabble DB – web-based database application • Cmsbox – a content management system (CMS) made available by netstyle.ch for the Swiss market. ==See also==