I am trying migrating from EWS Apis to microsoft graph Apis and trying to refactor my code. Here is the my doubt:
In my application, All create/update/get meeting synchronization functionality is currently implemented using "microsoft.exchange.webservices.data.core.service.item.Appointment" class but since Appointment class in graph is still in beta version that cannot be used in production.
So I have started implementing all the functionalities using "com.microsoft.graph.models.extensions.Event" class.
I am not sure of the difference between the two and also unware of the impact it may have on my application.
A explanation about difference and impact would be very helpful.Thanks in advance.
The event resource in Graph is the equivalent of the Appointment item in EWS. There is no appointment resource in Graph. There is a bookingAppointment resource in beta, but that is specific to small businesses using a booking service.
In short, you should be migrating your code to use the event resource.
Related
I started to develop an ASP .NET MVC website that connects to Dynamics 365 implementation.
The way I connect to Dynamics 365 is by using a separate Data Access Layer in my MVC website that make calls to Dynamics 365 every time I wanted to retrieve/create/update entity.
So every time I wanted to retrieve, for example, a list of Contacts from Dynamics, I will create an instance of OrganizationService using CRMServiceClient class from the SDK, and use it to query the CRM.
If, in another time I needed to update an entity, I will again made an instance of OrganizationService and use it to update the data in CRM.
Basically, every operation I will always create an instance of OrganizationService and query the CRM.
Is this the right way to do it? Are there any other approaches that I can take that can have better performance?
You are probably better off creating the OrganizationService once, then storing it in the application state. I don't have any empirical evidence for this, but I believe creating the service object can take a while.
Adxstudio (who created Microsoft CRM portals before they were acquired by Microsoft) also used a cache layer for data retrieved from CRM, to reduce the number of queries sent to CRM and improve overall performance.
Probably worth profiling the performance of both of these to see if the additional effort in storing the objects in memory is worth it in your scenario.
I want to know if there is a way to create a REST API that can be easily integrated in an existing system. Specifically what I mean, assume we have an existing system for an e-commerce website and my API is trying to automate/facilitate the process of adding items to a cart and purchasing. I know that some systems offer an API to do that but what I want is for the existing website to use my API and integrate it into their system regardless of its database architecture. Is this possible in any way?
P.S. if anything is unclear please let me know to update the description with more information.
Are there any indications that the Valence API would include tie-ins to the competency function? I'm thinking something akin to polling D2L for a competency report of a student indicating completion at various levels (a singular competency, or some hierarchy). Presently there doesn't seem to be anything in the documentation related to the competencies function. Or if it IS there in some form its not jumping out at me where it lies in the shadows.
http://docs.valence.desire2learn.com/reference.html
Awesome competency reporting, including making flexible reporting available via Valence is precisely where we at D2L hope to be hitting in the future, but as you discovered, is not available quite yet. We are initiating a wider cross-product project now to better support competencies & learning outcomes, and this request is noted. That said, I'd also encourage you to ask your LMS admin to send in this feature request via your D2L Account Manager.
I am doing some research on Grails and writing about what the future holds for it..
Something interesting jumped out in the RoadMap (http://grails.org/Roadmap)
GORM for REST
Anyone with more experience with Grails than me know what this would entail?
I am guessing some sort of CRUD operations through Web Services instead of using Hibernate to connect to an SQL database?
there is a JSON RESTful API for GORM which gives some insight on what GORM for REST is like:
GET on /context/api/domain-class-name returns a list of domain objects (possible arguments are the same as for the DomainClass.list() method argument map)
POST on /context/api/domain-class-name creates a new instance
GET on /context/api/domain-class-name/id retrieves the given instance
PUT on /context/api/domain-class-name/id updates the given instance by ID
DELETE on /context/api/domain-class-name/id deletes the given instance
As far as to RESTy GORM that is scheduled for Grails 2.0, here is the GORM Virtual REST domain objects discussion on Grails mailing list:
I am currently evaluating the use of grails to connect to other backend systems. Would it be possible to let the domain layer talk to CRUD REST services instead of a Database? It would be a bit like a XML backend.... We have got a very big backend where it is difficult to implement business logic, but we can manage to provide restful services. My idea is to have grails as a business / web application layer on top to deploy various systems to cross platform
This feature is scheduled for development for Grails 2.0
-- Graeme Rocher
I think the intent is to apply the scaffolding pattern to a RESTful API out of the box. There has been a JIRA entry around for several years for this.
Resulting JIRA: http://jira.grails.org/browse/GRAILS-2823
I also wouldn't be surprised if they took the dynamic finder idea and applied it to URL patterns.
GET /book/findByTitle/Dune
or
GET /book/findByTitle?title=Dune&format=json
or something like that.
I don't know exactly what is on the roadmap, but I imagine that the final product will have scaffold functionality (list,view,create,update,delete) through a RESTful interface plus some URL patterns that correspond to what you can currently do with the dynamic finders that GORM provides.
Take a look at the JAX-RS plugin. I suspect that will be the kind of thing they use.
Not that I want to rain on the parade but why would I use REST for accessing database rather than directly through hibernate. It's bound to slow down the DB access.
I am working on an ASP.NET MVC project and I am trying to get it integrated with facebook by using facebook connect API. Now, I am having a small problem in imagining how the conceptual layout would be. I am using the repository model in MVC, I have my own DB. I want to be able to fetch user’s information from FB, and maybe store their fb_uid in my database (is that legal anyway?) I also want to be able to post stories into user’s mini feed. I have a model class called User; this class has to be filled with data from both my internal DB, and FB database. I have repository classes to communicate with the database, and I don’t really know where/which part should communicate with FB? I thought of using the FBDeveloperToolkit, but from what I have read in this forum, the toolkit is a bit out of date! I don’t know if I should use XFBML and pure javascript functions? And if yes, how can pull the data back to my DB, for example user’s fb_uid? And does that mean I will be directly calling the API functions from my presentation layer?
Can anyone please help me in this?
Thanks!
I would suggest a FacebookService layer that implements a subset of functionality you need from the Facebook API. In the DDD world it's called an Anti-Corruption Layer.