Latest News
    Forthcoming Products
Existing Customers
    Comedy Webcam
  Pro Upgrade
    Reverse Proxy
  Learn HTML
    Wyn32 FTP
    Batch JPEG Resizer
    Manager Tree
    Buzzez Closed BETA
Bits and Bobs
    Instant Delivery
    Reciprocal Links

at32,Wyn32 2002
[ Home ]
Technology: at32 Webserver - fast, stable, low overhead

at32 Webserver

Not available for public release, at32 Webserver is an internal project tasked with providing maximum web application performance, stability and use of available resources.

at32 Webserver is based around the concept of fusing the server and web application into a single entity for maximum performance, control and stability.

Applications using at32 Webserver


Why doesn't the at32 website use at32 Webserver?

at32 Webserver is aimed at specialist projects, conventional tasks such as simple websites are better served by more flexible mainstream products.


From 29th March 2005 this website now runs on an adapted version of the server engine and even though not optimised for this type of role has coped very well!

Technology: at32 Scripting - fast, flexible, simple

at32 Scripting

at32 Webserver supports our internal scripting mechanism, and will first be used in our Web Community Project.

at32 Scripting is *not* an alternative to other server based scripts, but is a way for administrators or users to achieve much more control and customization potential without programming intervention.

Think of it as a combination between a scripting language such as PHP, and a conventional admin interface. at32 Scripting will commonly be used in user interface roles, but without the administrator requiring detailed knowledge of more complex general purpose scripting languages.

Like much of our work, performance is our main concern. All scripts are compiled for maximum speed and heavy performance testing is utilised to achieve speed far quicker than full scripting languages.

Introducing: Wyn32 - a Graphically Orientated Interface


One word that best describes our Interface API, which we plan to use as an alternative to regular Win32 when and where possible.

Why Wyn32?

If you're a programmer - you may well find regular Win32 and it's components just fine. For most tasks, we certainly do too. However, more often than not out projects have unusual requirements that require the creation of entirely new components.

This is fine, and in most cases regular Win32 is competent and flexible enough to allow us what we want to do. But for the more performance orientated and innovative amongst us always want more - and Wyn32 provides us with a platform to give more of everything.

Wyn32 in Action

Wyn32 bypasses Win32's GDI routines and instead works on manipulating 24-bit raster memory - often several Mb's of data a second.

Despite this thru-put, the interface is remarkably swift - running at a competent rate on any modern PC made within the last 5 years, and also hugely compaitable (we had it running on a dated 486 in testing with no stability issues).

Because Wyn32 renders directly into memory, conventional commonly used Win32 components were no longer compaitable and thus a new set had to be created from scratch. Much attention was spent on mimicking the core features of existing components, as we did not want to end up with an interface with which people were not familiar with.

We wondered if it was all worth it, but now we have an interface for component writing that has unlimited potential. As we control the screen drawing as well as components however, all sorts of unusual and innovative new ways of interaction can be developed.

What is it Good For?

As we come from a game developer background, the API interface is aimed mainly at our leisure or "non-serious" titles... at least for the moment. However, it's also useful for graphically orientated applications such as graphics manipulation software.

Wyn32 FTP

Our first Wyn32 application was Wyn32 FTP. Strictly speaking, Wyn32 is not suitable for the demands of being an FTP client - the managment and display of long lists and the absence of any need for graphics indicated that this would be a tough test. However, the API performed well - and as we knew this would be it's toughest test - future developments for which Wyn32 was specifically developed for look promising!