arl's products

[this] [up] [top]
Contact?!

This file is obsolete: use this [here]


What can I do for you? Why not contact?


CV English | Finnish
  
G*F (Generic frameworks) Generic Java frameworks for:
GAF - Applets: containing Nasduk viewer
GCF - Configuration: container, context, and media classes for handling Java system configuration.
GEDF - Encode/Decoder: stream encoding decoding interfaces and tools. [not yet ready]
GLF - Logging: Java system logging framework.
GVF - Version: Java class versioning system. Tools for finding out class versions
GSF - Server: Java servers for authentication/authorization [not yet ready], webcam & connectors - webcam multiplexer.

Dependencies: uses aow interfaces for abstraction.

References: GSF + GAF used at
  • www.lumimaailma.com
    with HTML window which uses push operation.
    with applet window Nasduk viewer © arl. Handles push with browsers not capable for it.
  • Now 11/2003 the system has been up 1 year 24/7 without any problems or failures. No "reboots" at all. Even thought the camera had some problems due lightning the system worked (camera was fixed, the system showed communication error image).
    The system contains quite have logging which is cleared using cron. Logging helps to find out bugs, but was left there because no bugs were found and we did not want to restart the system.
  • Nasduk viewer was created because Gambozola which was used earlier is quite buggy (depending directly fixed header formats) and it contains too much features: when we are watching webcam we really want to watch it, and not play "url games". Also Nasduk uses Java awt image better.

Where to use: Java system parametering, large system configuration, for supporting multiple languages, integrated into your software, to have multiple configuration file formats supported, to have multiple configuration sources to be used simultaneusly (like files,xml,ldap,db, or other sources), to integrate program parameters from multiple sources (commandline,servlet, etc.).

Customization: all of the frameworks are coded using desing patterns like factory, adapter, etc. GVF uses lazy evaluation. JUnit test cases.

Pricing: depends on your installation

Keywords: generic,java,framework,configuration,logging,version,webcam,multiplexer
  
mail conversion tool Tool for converting iPlanet mail boxes into Cyrus.
Supports Cyrus full dir hash (--enable-fulldirhash) mode (when you need to have more than 30K users).

References: 30K+ mail accounts converted in a run, ~2GB data within ~24 hours.

Where to use: Need to change email environment on the fly.

Customization: sources are written using Perl. @keyword@ evaluation is used for customer dependent information and for testing (naturally).

Pricing: depends on your installation

Keywords: iplanet,cyrus,qmail

Todo: conversion from mbox to cyrus hashed accounts (for customer need), IMAP protocol based conversion, Java based conversion tool - (using aow library utilities)
  
backup tool/system Backup system without management or operator
Is created using small sh and perl scripts.
Is ideal solution for self service environment.
Can be used for work/project progress analysis, by following file modification activity.
No need for RAID systems - incrementals will be backupped to other disks or other systems.

References: Semantically same kind of system was used in an office with ~30 client machines connected to server. No other backup software was used.

Where to use: In an environment where is not possible to have an operator, small programming houses etc.

Customization: @keyword@ evaluation is used for customer dependent information.

Pricing: depends on your installation and needs.

Keywords: backup
  
provisioning framework Provisioning users into unix services; "normal" unix software within a larger system and there's need for integration tool. This integration tool is provisioning framework.
Currently contains user intefaces: servlet, command line, and jdbc
Currently contains independent modules: transaction and application frameworks
Transaction framework: arl
Application framework: arl
Dependencies: uses GCF, GLF, GVF.

References: provisioning framework used at
- in a largish email system where through www portal provision commands are sent to provisioning framework using http. email system implemented with qmail + cyrus, but provisioning framework is really independent of underlying unix software. Application framework adapters (used through transaction framework) use perl scripts for provision commands.

Where to use: When implementing large systems containing standard unix software to be integrated.

Customization: Java & design patterns. multilayered design.

Pricing: depends on your installation

Keywords: unix, linux, tomcat, servlet, provision, mail, cyrus, qmail, transaction, commit, rollback
  
consultancy [hire?] Java coding [x], Linux/Unix system consulting [x], Refactoring
Designing & Planning, System structural analysis, Refactoring analysis
Project management, Systems design, Technology analysis

Larger projects: Use my partner network as a solution: up to 20 person projects with project leading, system administration, architectural desing, and coding. Target area: servers & embedded solutions.

Interviews: You sell your media, I sell my work.
  
used technologies XP extreme programming: some points of it are usefull some not.
design patterns is the base for my designing/coding.
testing using Junit (with own wrapper) for component testing, integration testing, and for system testing (as far as it's usefull).

Java [5+ y] is usefull for system independent coding. Used java.{awt,io,lang,lang.reflect,math,net,sql,text,util,util.jar,util.zip}, javax.{swing,}
Perl [10+ y] is usefull for system adaptation instead of shell scripts.
C/C++ [15+ y] for some cases.
asm [20+ y] for some cases.
Linux [10+ y] is inexpensive and reliable platform for commercial servers, and programming.

network programming [15+ y] servers and clients, WWW [10+ y], FTP etc [15+ y] low level/protocol coding.
embedded systems [15+ y] developing system and prommer for customer needs.
real-time systems [15+ y], also true-time systems.

aow creating base ideas as interfaces and supporting libraries within aow system, and commercial products on top of aow classes.
  
todo
on-going projects
CMS/EDMS: on-going project
video: based on webcams, system for surveilance. based on aow tools already created.


© arl | Contact?!