Closed GoogleCodeExporter closed 9 years ago
Rupesh:
execute http://hostip:1502/o should be execute http://hostip/o or execute
http://hostip:80/o
1502 is the Socket Server that communicates with the devices. Web requests are
still on port 80 which what it should be
Original comment by openmobs...@gmail.com
on 20 Jul 2011 at 7:32
Thanks for response.
I was mostly trying port 8080 as JBOSS works on that.
Let me introduce myself,
I work with Dell services and currently evaluating diff MEAP solutions to
offer to our customers.
It would be nice if you can provide little information ob below
1. Sync solution
2. How to connect to diff Enterprise Databases like SQL/Oracle/SAP/DB2 etc
3. how Appcelerator is integrated
4. Stability of the solution
5. What are licensing terms..I do not understand Eclipse license in detail
Based on above A's, we will offer diff solutions to our customers.
I liked OpenMobster among the rest and would be great to get details so as
to make pitch in front of Management
Rupesh
Original comment by rupesh.j...@gmail.com
on 21 Jul 2011 at 5:23
Hi Rupesh
My comments are inline
1. Sync solution
OpenMobster Sync Solution is very stable in terms of performance and
robustness. It can handle 4 types of Sync although the developer never has to
worry about those details. The change tracking on the phone takes care of all
sync requests. To get an idea for what scenarios are covered, I would recommend
looking at the test-suite stored in device-agent-simulator module. The Sync
engine for modeled after the SyncML spec. Its not SyncML compliant because I
had to add some innovations related to App Sync instead of BlackBox Sync that
SyncML was originally designed for
2.How to connect to diff Enterprise Databases like SQL/Oracle/SAP/DB2 etc
You will need to use the Channel component to expose these Enterprise services
to the Sync Engine. On the device side they will be accessible using the
generic MobileBean interface. I would recommend looking at the CRUD sample app.
That one mobilizes a Hibernate based database. The same rules will apply
architecturally
3. how Appcelerator is integrated
Appcelerator is our write once run anywhere layer. Using Appcelerator you can
write your app in javascript, and have a single codebase for multiple
platforms. From an OpenMobster standpoint, its API such as Sync, RPC, and Push
are made available in the javascript layer. This done using their Module
Development Framework which bridges javascript layer with the native layer.
Appcelerator is a very important investment and we will continue to expose our
API as it evolves.
4. Stability of the solution
Every tagged release is put through an extensive test cycle. You can tell from
our codebase how many tests are run. We try to test at the minutest
detail/scenario. The software is not perfect though. It never is, but as bugs
are reported we schedule them for release pretty fast. From a performance
standpoint, we have hit a default Java Heap with no optimizations with 1500
devices and it did not budge. The hits were full blown two way sync sessions.
5. What are licensing terms..I do not understand Eclipse license in detail
I am not a lawyer but this is what I understand and this is how I expect to
conduct business. With the Eclipse license you can use, re-distribute, and
bundle without any restrictions. Your solution can be closed. Thats why its
called the Business Friendly License. The only restriction is that if you
change the OpenMobster codebase, then you must make those changes open. This
IMO is hardly an issue. I would check with one of your lawyers to double check
my understanding
I liked OpenMobster among the rest and would be great to get details so as
to make pitch in front of Management
Thats great. For any more questions please feel free to email me at:
openmobster@gmail.com
Thanks
Sohil
Original comment by openmobs...@gmail.com
on 21 Jul 2011 at 3:17
Original comment by openmobs...@gmail.com
on 1 Aug 2011 at 4:02
Original issue reported on code.google.com by
rupesh.j...@gmail.com
on 20 Jul 2011 at 12:28