This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal



Feb 18, 2014, 7:31 PM
37 Posts

Advantages and disadvantages of different ways to surface REST data

  • Category: Performance
  • Platform: All
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags:
  • Replies: 3

I find myself doing more with REST and JSON data. I love the work on the extjs grids and the full calendar that people in the community have done. Really amazing work. What I did notice all the different ways to make the data available. Keith Strickland used a java parser for the data, while Mark Roden used javascript for his. I have been leaning towards using Domino Data Services and a view to create my data, in fact that is what I used to create the data the full calendar.

I would be very interested in hearing everyone's thoughts on the different methods and if anyone has any performance numbers I would be very interested to see those too.

For me a notes view seems like the easiest approach, but gives you the least amount of flexibility (still really powerful)

Feb 18, 2014, 7:47 PM
366 Posts
The simple answer

Keith is a Java developer.  Mark is a JavaScript developer. (I know them both personally so I feel pretty confident making this statement) :)

That does not make one "better" over the other.

If this is a strictly performance question then as a rule you are going to get the best performance with a mostly Java solution (where Java does the heavy lifting of sourcing the data).

That being said, if Java is a barrier to entry, the use the javascript approach while coming up to speed on Java.

Bottom line is if the JavaScript solution was not "performant enough" then folks would not be using it and ALOT are.

 

Feb 18, 2014, 8:48 PM
37 Posts
java js DDS

Paul, Thanks. What do you think about Domino Data Services to create the data? I would assume that using a native Domino API would be much faster than Java?

I understand that "better" is subject to opinions, and I was kind of looking for those too.

Java was the barrier to entry. I tried using keith's code and ended up crashing the HTTP task on my server. My own fault, but you have to break a few omelettes before you can make any eggs </jk>

Feb 18, 2014, 11:47 PM
366 Posts
It depends upon the target for the data

Unless you need the json/xml then there are more efficient ways of getting to the data natively in XPages.  I view the rest services more for "external" consumption than for working with the data "locally' in my application.  

I would encourage you to keep "breaking those eggs" as the rewards are typically very high !!

 

 


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal