Duong, if your question was for me - i'm seriously considering going open source with Nimbits. There are a few reasons i have to keep parts of it proprietary. I will almost certainly release to source to all of the client interfaces - in fact, i put a lot of free code on my blog: http://nimbits.blogspot.com/
The whole point of nimbits is to provide a single place to store and share historical data - and it provides web services you can program on top of - i'm posting code on how to do this every day. There are a couple of parts of the backend platform i spent so much time on, it's hard to open it up to the world - but it gives me something to think about. Thanks for your post. Ben On Feb 14, 11:43 am, John Denley <[email protected]> wrote: > LOL, well firstly my source code is probably not at all well written! > > I am looking to employ a "real" programmer to completely rewrite my > application in the next few months though, assuming that someone doesnt buy > us! ;) > > On the other hand if someone can either point me to a really good website, > or write to me "offline" and explain to me why open source is a good way to > go, and how I can protect my product from being stolen if I do put it open > source? > > On 14 February 2010 16:34, Duong BaTien <[email protected]> wrote: > > > > > Hi: > > > Is there any thought of Sharing the source code for the community > > benefits? It is very easy with athttp://code.google.com/p/yourProject > > > Duong Batien > > DBGROUPS and BudhNet > > > On Sun, 2010-02-14 at 06:48 -0800, Benjamin wrote: > > > Hi Cris, thanks! > > > > To be honest, i've been working on a data historian for over 6 years > > > in one form or another. I always ran into problems with either > > > scalability or delivery. Always ended up having to tell a client they > > > needed to build a huge server to run my code - and i was just another > > > expensive historian. It wasn't until the advent of cloud computing > > > that I was able to deliver the service. > > > > I couldn't even begin to calculate how much time i put into the > > > compression algorithms, calculation engine and all of the things i put > > > into the back end and how much time I put into the app itself. Since > > > the hard part was done, it only took me two days to put together the > > > android piece, and about two weeks to create with the windows desktop > > > client. That's the great thing about SOA. > > > > -Ben > > > > On Feb 14, 5:43 am, Chris Lercher <[email protected]> wrote: > > > > Looks good, great idea! First question: How many hours did you invest > > > > to develop the AppEngine/GWT app? And how many additionally for the > > > > Android interface? > > > > > Chris > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%2Bunsubs > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
