Dear Smalltalkers,
New Swazoo 2.1 is released, with an easier startup as a main new feature. Now you can start simply by: SwazooServer startOn: somePort and Swazoo will start listening on all IP interfaces on your machine. It will also ignore host in web requests. This is very handy for running Swazoo behind load balancers. This version is also much improved in terms of serving directly to the wild wild Internet. It is available here: * VisualWorks: in public Store: Swazoo 2.1, also as a parcel on forthcoming Cincom CD See http://www.swazoo.org for more. Swazoo can be now used as a web server for two web frameworks: * Aida/Web: On Squeak and VisualWorks: load version 5.4 or later * Seaside 2.8, 2.9: On Squeak load from Universes (Web development beta): Seaside-Adapters-Swazoo For instance, on Damien's squeak-web you can now run both web frameworks side by side: SwazooServer demoStart then open http://localhost:8888 SwazooSeaside startOn: 8088 then open http://localhost:8088/seaside Best regards Janko Mivšek Maintainer of Swazoo |
On Mon, 07 Jan 2008 12:15:53 +0100
Janko Mivšek <[hidden email]> wrote: > Swazoo can be now used as a web server for two web frameworks: > > * Aida/Web: On Squeak and VisualWorks: load version 5.4 or later > * Seaside 2.8, 2.9: On Squeak load from Universes > (Web development beta): Seaside-Adapters-Swazoo This begs for running a benchmark between the "officially supported" Seaside/OpenTalk and Seaside/Swazoo. Any takers with a litte bit of free time? s. |
Hi Stefan,
Stefan Schmiedl wrote: >> Swazoo can be now used as a web server for two web frameworks: >> >> * Aida/Web: On Squeak and VisualWorks: load version 5.4 or later >> * Seaside 2.8, 2.9: On Squeak load from Universes >> (Web development beta): Seaside-Adapters-Swazoo > > This begs for running a benchmark between the "officially supported" > Seaside/OpenTalk and Seaside/Swazoo. Any takers with a litte bit of > free time? First thing to do on VW right now is to port Phillipe's SwazooSeaside adapter from Squeak, so that Swazoo 2.1 can be run with Seaside on VW at all. Any takers for that? Best regards Janko -- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si |
I have an application with runs fine on Windows that I'm porting to Linux. One of my calls to read an external file using the dllcc interface works fine on windows but on linux returns a Unhandled Exception: exception occured (#11 3011236663). I scanned the doc and in the DLLandCCConnectGuide.doc Chapter B, there is a table of error codes that says the error codes are platform dependent but that for windows an error code of 11 is ERROR_BAD_FORMAT. I grepped the header files on the linux box but haven't found 11 as a error code anywhere. Does the 11 mean that the C code is returning a bad format? Thanks, Jim |
Jim,
Most likely the C code is actually crashing possibly due to an incorrect argument (like uninitialized memory in one of the arguments, or one of the arguments in the C call prototype in Smalltalk being defined as void * rather than a proper type - a bad side effect of the header file parser in DLLCC), but the exception handling on Linux sometimes returns this kind of error instead of a core dump. Most of the times I see such errors on Linux, a retrying the same C call does actually result in a core dump (which is often easier to analyze. I hope this helps, Nick Jim Harsh wrote: > > I have an application with runs fine on Windows that I'm porting to > Linux. One of my calls to read an external file using the dllcc > interface works fine on windows but on linux returns a Unhandled > Exception: exception occured (#11 3011236663). I scanned the doc and > in the DLLandCCConnectGuide.doc Chapter B, there is a table of error > codes that says the error codes are platform dependent but that for > windows an error code of 11 is ERROR_BAD_FORMAT. I grepped the header > files on the linux box but haven't found 11 as a error code anywhere. > > Does the 11 mean that the C code is returning a bad format? > > Thanks, > Jim > > |
Free forum by Nabble | Edit this page |