I am not sure if this is a genuine question but I will try anyway.
The Kaa platform promises an open source IoT middle-ware apparently backed by a relatively large company. They suggest StackOverflow as the forum and place to ask about it, but for a few months basically no questions have been answered. Their older forum, also sounds kind of abandoned.
Does anyone have any idea why?
If not I would like to use this question/post to raise some awareness, discussion among enthusiasts, and hopefully hear the developers' voices.
I believe in an open source project it is always important to have some feeling about the state of the project, and the community behind it (which, as the company states on their website: should be vibrant) before committing some development/testing time. Kaa sounds as a great alternative for IoT projects. I would like to hear some of the opinions from other developers who are using Kaa about this issue.
Thanks!
pepgma, Mayur Patel,
Andrew Kokhanovskyi here, CTO at Kaa. First of all, please let me apologize for the lack of responses in public forums that you have experienced in the last few months. As you may know from our recent webinars, posts, etc., we are now working hard on the next version of the Kaa platform: codename "Banana Beach". It is because of the push to get the significantly improved version of Kaa to the early adopters that our engineering team has been having difficulties supporting all of the community requests lately.
Having said that, we truly appreciate your support of the Kaa open-source platform. As a token of gratitude, we would like to offer an invitation code: "AA-ADOPTER5" that you can use to register for the early access to Kaa BB here:
https://www.kaaproject.org/apply-for-early-access-to-kaa-1-0-banana-beach/
On our end, we will make sure that you will have a chance to be among the first ones to experience the new version of the Kaa platform.
--Andrew and the Kaa team
Related
A friend of mine asked me to take a look at using Flex Licensing to protect the distribution of her software. I've spent a bit of time going through the flexera website to see what information I could glean, but I find nothing that tells me how one actually connects their software to the licensing system. Is it an API that allows me to build the functionality into an application? Is it something else? I decided to not put too much time into getting frustrated before asking here if anyone had any experience with this or similar licensing systems.
Regards and thanks!
To answer your question, yes, there is an API.
You can request a trial of their FlexNet Publisher Software to see if it is something you would like to work with. However, I would recommend you contact them to see if their pricing model would fit into your friend's development budget.
Brief relevance of the question.
I am working on a project, which is my first tech start up. I found the framework very fascinating, but i am afraid that it would lead to troubles because of certain drawbacks that are not meeting my eye at the moment. I would appreciate the Stackoverflow community's perspective on it.
The Project i am planning will be function as a Question & Answer forum much like Quora or Stackoverflow for certain domain of professionals.
Meteor is appropriate for almost anything - that part of your question is a bit broad, but I refer you to the Meteor Trello roadmap for features that still need to be developed.
That said, I think that if you can develop anything using Rails/PHP/whatever, you can make it in Meteor and in 1/10 the time.
I've been recently tasked with leading an effort to improve our input (and output) validation with OWASP recommendations and PCI compliance in mind. In the process, I'm trying to assess the value of the ESAPI.NET project which does not appear to have seen any activity since the spring of '09 and as it stands is incomplete.
Does anyone have experience using or extending ESAPI.NET v0.2? Is it a good starting place today for building out an infrastructure to address the targeted vulnerabilities?
FYI: I am looking at MS AntiXSS which, of course, only addresses a portion of ESAPI's scope. We already do a good job with SQL injection though there are improvements we need to make.
(If someone wants to create an ESAPI tag, feel free. I don't have the mojo.)
Looks like there were a couple updates last week: http://code.google.com/p/owasp-esapi-dotnet/source/list
You might contact one of the project leads on that list to ask what's going on.
NOTE: 05/26/2012: the last update on that project was dec 4, 2010. Yes, it is dead.
It looks like ESAPI is dead period. There's nobody using it, there are no questions, no forums, no information, nothing. The listservs (what is this, 1996?) are barren too. The documentation is terrible and the samples in the swingset don't work (server that installs is HTTP not HTTPS, and no transactions can be made in HTTP mode).
Seems to be a dead end project.
The project itself seems dead there are however some people who maintain a github copy with several (minor?) additions...
https://github.com/haldiggs/owasp-esapi-dotnet
https://github.com/jstemerdink/owasp-esapi-dotnet
I am undergoing BizTalk server training in my company.
I have almost 6 years of experience in both Microsoft and Open Source like PHP mostly in web applications.
Does it make sense to learn Biztalk server for my future career?
In short Will it help me to improve my profile?
Please advise/suggest.
Learning anything that is an active and vibrant technology will help you and your career. I don't see how this could be qualified as a negative in any aspect.
Even if this particular product goes out of use, it's useful to understand the problems it is intended to solve and the general approach. Don't get too hung-up on details though.
You may want to look at New Features in BizTalk Server 2009. It's not dead yet.
i have been doing BizTalk server development for years and it has most certainly helped me be an early adopter of the SOA / Contract first / Loosley coupled application fad that is sweeping through the industry ... why? well because as BizTalk developers we've always done this stuff. it aint new to us.
so yes, learn it. it can't do you any harm at all!
My company (a large organization) is developing a "road-map" for evolving their rather old, tangled confederation of systems to an SOA model. A few people are pushing hard for using Websphere Integration Developer and Websphere Process Server as the defacto platform for developing future applications...because they feel IBM is a stable vendor, the tools are made for the enterprise, they drank the "business agility" BPEL kool-aid, etc.
Does anyone have positive or negative thoughts on this platform? Do the GUI tools help eliminate monotonous/redundant coding...or just obscure things and make things harder to maintain? Basically, do the benefits justify the complexity?
My experience with the IBM Java tool set is pure pain. Days to install lots of different versions of different components all incompatible with each other, discover a bug in component A get told to update to see if it fixes, updating component A breaks component B and C, get told to update these etc.
I find Eclipse with out the IBM extensions far more stable and quicker and provides more features (as its stable versions are a couple releases ahead of WID/RAD).
I would advise against going the IBM way for development tools. As for process server I have less experience but the people in my team using it seemed to enjoy it as much as I enjoyed WID. not a lot.
So far I havent been impressed by any tools with the "SOA" and/or "BPM" labels on them. My "roadmap" would be very very iterative to see some results with the archetecture as fast as possible while trying to grab some of the easy fruits. That way you gain your feel for what works for you and your people.
I would never let any vendor push me anywhere in the "scuplturing" of the architecture.
I agree with other users complaining about WID. The only reason we are using WID is that a decision was made a while back to use IBM products across the board by our sales department.
That's right, our sales department made the decision to use IBM products.
Development has been painful and frustrating. We have lots of stability problems with Process Server, sometimes it doesn't want to start or shutdown properly. Yeah you can easily draw processes in the IDE, but most any toolset provides that functionality these days. It is nothing special or unique to WID or IBM. IBM is a few iterations behind mainstream.
There are plenty of open source implementations out there that offer great support. Checkout JBoss or RedHat, they are pretty good. If that doesn't float your boat, you can always use Apache tools.
Walter
Developers don't choose WID, WMB, or WPS. Managers do, because IBM is a "stable vendor".
Look at JBoss, or K.I.S.S.
WID/WPS is actually pretty simple. The original intention was for analysts and business people to "compose" services (DO NOT LET THEM DO THIS!) so the UI is simple and easy.
Most of the work will be in defineing and implementing the back end services which depending on the platform will mostly involve wrapping existing code in SOA service.
The most important thing to bear in mind is that SOAP is technoligy and SOA is an architecture and a state of mind.
There is a zen to a succesful SOA implementation. Its all about "business services", if you have a service that you cannot describe to a business user in less than six words you have done it wrong! Ideally the service name alone should be enough to describe the functionality of the service.
If you end up with a service called "MyApp.GetContactData" described as "get name, addresses tel fax etc." then you are there. If You have a service called MyAppGetFaxNoFromOldSys" described as "Retrieve current-fax-nmbr from telephony table in legacy system" you are doomed!
Incidently most of the Websphere tooling for WS* is pretty nice. But I would recommend the very wonderful SAOPUI tool from http://www.eviware.com which is very good for compsing/reading WSDL based messages and also function as a useful test client or server.
Do the GUI tools help eliminate monotonous/redundant coding...or just obscure things and make things harder to maintain? Basically, do the benefits justify the complexity?
As a Developer, I find the tools at varying levels of being bug free. 6.0.1 was a pain, 6.2 is so much better. But once you develop with the tool, there is minimal effort to maintain it. I develop in hours what java developers take days to do. It is also easy to maintain as changes can be made very quickly. I cannot answer your question from the perspective of an architect or a Manager but i would agree with comments of some others here.