Recently I was looking for SMS (mainly) gateway, free, and preferably, open source. I ran into Kannel which fits my needs so far, and more. However, I was hoping for something that is Windows-based (Kannel is Linux-based)... well, I know Kannel can be compiled and run using Cygwin, but it won't be as reliable as on Linux.
Does anyone know about similar thing on Windows? I'm not looking for a full-featured enterprise solution, something as simple as Kannel (and engine with few API's) is okay with me.
http://smsrobot.sourceforge.net
Cygwin is not necessarily less reliable. If Kannel works on that, my advice would just be to use it.
I know one working Kannel installer build (1.4.3 and CVS) for Windows prepared by archi.tech company. It's built using cygwin and includes some patches for better stability.
This is available here: http://www.thearchitech.com/downloads/
Related
I'm experimenting with using node.js beyond the server as a general-purpose scripting and application programming language.
One project on my TODO list would be a Windows service so I'm considering tackling it with node.js
I believe I have seen some kind of Windows API bindings for node.js but I don't know how complete or mainstream they are. (I'm willing to contribute!)
What would it take to implement a Windows service in node.js? (Trivial example appreciated.)
You should be able to do this very easily using Winser.
Try node-windows. It's similar to WinSer, but has more options.
Is Cygwin considered robust and safe enough to be used on enterprise applications?
Do you know Enterprise applications that were developed or using Cygwin?
If you've been using cygwin - how often did you need support? Is there a fine-support for Cygwin? how well was the support you were given?
Thank you very much.
Why on earth would you even consider cygwin towards any sort of enterprise application? Even their site directly gives multiple signs it shouldn't be used for anything critical. You can't run native linux apps and you have to rebuild your app from source if you want it to run. It won't make your apps able to use any *nix functionality like signals, ptys, etc. All it is is a slim Linux type API layer....to answer your question, I don't think anyone would want to use cygwin in an enterprise application.
Like Maz asked, why wouldn't you just run linux? What potential benefits would you ever see coming from cygwin in an enterprise environment?
The best answer to your question may be obtained from the Cygwin web site. The answers obtained there come directly from the maintainers of the Cygwin DLL and ported software.
I'm wondering if anyone has any information or speculation as to when or if there will be a native windows version/port of Node.js.
There is an ongoing effort to provide a mingw port of Node.js. Version 0.3.6+ can be build that way.
However that is still experimental and anything but ready for more than quick and dirty development. Even in case this version matures, I suppose that it will always lag behind the *nix versions, mainly due to the fact that the event loop implementations that Node uses were originally written for those systems and APIs.
The windows version may become stable for development at some point in the future, but I hardly doubt it will ever be usable for production.
July 2011 Update:
#nodejs v0.5.1 is the first to ship with an official Windows executable. We're hoping to get some good feedback.
Microsoft has officially gotten involved with joyent in making node.js work natively on windows.
If one or two Windows C++ developers would put in the effort, then they could fill the gaps in the native Windows version and produce a node.js implementation that would be usable for production.
For now, there is a working Cygwin version and I don't know of any testing that shows it to be unsuitable for production. It certainly works fine (version 0.5.0pre) for development.
Have a look at:
http://www.rafaljonca.org/d/nodejs-windows
Which is based on the work of these guys here
http://node-js.prcn.co.cc/
Both good ways of getting node on windows if you dont have cygwin. However after many heartaches I found developing Node stuff on windows easiest by just using virtualbox with the ubuntu image.
Tnx
GT
I am strictly a Windows Dev and I have wanted to mess around with Node.js for quite a while.
It looks like Microsoft, Rackspace.com and the Node.js team are planning on working together port Node.js to Windows.
So, it's not hear yet but it should be soon. w00t!
The Official Node.js Blog
The first stable version has been released: Release details here.
Be sure to check for the latest version as the link above will go out of date.
I am trying to learn a little about driver development and my question is, which OS has an easier API to develop drivers with? Windows or Linux?
Remember that I am new to this.
Thanks
If you are doing this for learning (I guess its your case), then go for Linux, you will have a more general ideal on how an OS works, you will interact with low level implementation straight to the core.
If you are just writing a driver for a device, I recommend using Visual Studio under Windows, it has a lot of features that will really help on your devel.
I am pretty sure you'll get lots of Windows vs Linux war here, unfortunately.
On Windows, you'll get pretty good development tools, with some awkward stuff, but that you can get along with easily. API is documented provided you have access to a Windows Developer account. Remote debugging is supported and it helps a lot for these kernel stuff that are triggering BSOD so quickly.
On Linux, you'll need to get your hands more dirty. Rubini's "Linux Device Drivers" is a very good starting point. Openness will bring you more flexibility, and more understanding of what is happening.
This tutorial might be helpful.
It is about writing a simple device driver for linux.
My personal idea is Linux. You can see the entire code other than an API.
I think Windows is good.
Because it has a rich set of API's which is easier to use
Are there any equivalents in the Windows world for patch stack management tools like Linux's quilt? I'm trying to come up with some development workflows for our environment, which need to work on both Linux and Windows. I can come up with a beautiful system for Linux using quilt and the like, but unless I can find a way to replicate it on Windows as well (including pretty GUI's for all the command-line-phobic developers), I'm basically stuck.
Maybe Mercurial's Queues can help? I do believe they work in the Windows implementation of Mercurial, too.
I use quilt on Windows by way of Cygwin.