Thread: Intel abandons UMPCs?
View Single Post
iball's Avatar
iball is offline iball
2007-05-10 , 16:55
Posts: 729 | Thanked: 19 times | Joined on Mar 2007
#14
Originally Posted by Texrat View Post
Yeah, I intend to host my applications on a corporate intranet site using active server pages (ASP). I'll be coding most of it and using canned stuff (especially the functionality in SQL server 2005) where I can. I've got it partially working.

The main hold up for now is VPN. We have some guys developing a tool for internal use and it isn't quite 100%. Our corporate solution relies on SecureId cards so if an oss application was developed that worked with our system that would be ideal. The main problem I'm having now is resolving short server names into fully qualified domain names (fqdn)... I can't seem to get the development team to udnerstand how important that is to some commercial apps (they tell me *I* should always use fqdn, duh, but try telling every third party developer).
Sounds to me like something my "employer" has been doing for years now.
On our smartcards are our embedded PKI certificates and each card has a 10-digit number on it in front of @our-domain-name.
In Active Directory all of our accounts are mapped to this 10-digit code so we can login just using our smartcard PIN codes (PIN != 10-digit on card).
Microsoft did develop some hella-useful software that integrates all of this at our bequest, but I just don't see the same ease-of-use and deployment in any OSS offerings at the moment.
Problem is, using a hardware-based token for this - as well as via our Cisco 3000 VPN Concentrators scattered all over the planet - means we can't use small devices like the Nokia N800 tablet or Nokia N80i/N95 cell phones unless we somehow obtain a software token to use with the same.
Which my employer says isn't going to happen. Ever.

But lately the only thing we're using ASP and SQL 2005 for is with Sharepoint 2007.
For everything else we tend to use PHP and MySQL running on Server 2003.
I would suggest you start programming for that as it makes the code itself a lot more portable between varying server operating systems and hardware upgrades.
Add to that the capability for almost every single portable and non-portable web browsing machine out there to work with it versus ASP's more advanced functions generally only working well with IE 6/7.