In MVC for controller whether to go for JSP or Servlet???

Which will be better for controller... JSP or a Servlet.... will there be any difference in response time and performance.
kiran

I read somewhere that we can use either Servlet or a JSP, I wud like know whether there will be any difference in performance as such and i feel like using JSP as my controller rather than going for a Servlet cuz therez no need for me to compile and all and also there won be any other code in JSP like we use all the formalities for a servlet like for redirecting to a page we need to get the servletcontext and all.
so on the whole i feel like using a JSP is much comfortable rather than a Servlet... i just need to know whether there will be any difference in the performance and all...
thx in adv,
kiran

Similar Messages

  • Did not find repository information for controller

    Hi Experts,
    We are getting following error in Production system. Could you please tell what can be the root cause behind it. I know when someone deploys this error comes. But in Production No one is deploying any Application.
    Please tell me what can be any other problem.
    Exception occured during processing of Web Dynpro application  /material_wd/ChangeRawMeridianApp. See exception stacktrace for details.
    [EXCEPTION]
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ChangePackManualCompView
    at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:572)
    at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:548)
    at com.sap.tc.webdynpro.clientserver.uielements.adaptbase.AbstractAdapter.findViewElement(AbstractAdapter.java:124)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.handleUIElementEvent(HtmlClient.java:2037)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.updateEventQueue(HtmlClient.java:550)
    at com.sap.tc.webdynpro.clientserver.phases.TransportIntoDataContainerPhase.execute(TransportIntoDataContainerPhase.java:48)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingPortal(ApplicationSession.java:584)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:311)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.dispatch(ApplicationHandle.java:275)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:71)
    at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessActionInternal(LocalApplicationProxy.java:962)
    at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:297)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1638)
    at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:361)
    at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2062)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:220)
    at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:52)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)

    Hi,
    Some one might be deployed WDJ application with controller name ChangePackManualCompView which is already exist in some other application with diff name space
    Did not find repository information for controller
    Thanks,
    Sreeni.

  • HT1151 I WOULD LIKE TO USE MY PLAYSTATION 3 GAME CONTROLLER ON MY IMAC FOR CALL OF DUTY4CAN IT BE USED

    i wouu;d like to use my playstation game controller on my imac for call of duty is it possable

    Take a look at:
    http://www.mactrast.com/2013/01/how-to-use-a-playstation-3-controller-with-your- mac/
    MtD

  • Boot Error: Errata bits for controller 0x8086

    Seems to be a non critical error as system functions fine. But i noticed this only recently started appearing and not sure of exact cause. But I did some checking and did find this is the USB controler and each errata error corasponds to one of the built in devices which include
    each of the internal 5 USB hubs linking to the devices
    isight
    bluetooth
    keyboard/trackpad
    IR Receiver
    External USB hub (for hooking up everything else outside of comp)
    what's causing these errors is unknown, but the hub calling the wake state change is the IR Receiver hub. Anyone else have any experience with this? not experiencing any bad behavior devices work fine system stable, just a recent change i noticed i didn't observe prior.
    Sep 2 00:43:51 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Sep 2 00:43:51 localhost kernel[0]: USBF: 10.721 Errata bits for controller 0x8086/0x27c8(rev 0x2) are 0xe800
    Sep 2 00:43:51 localhost kernel[0]: USBF: 10.797 Errata bits for controller 0x8086/0x27cc(rev 0x2) are 0x5800
    Sep 2 00:43:51 localhost kernel[0]: USBF: 10.810 Errata bits for controller 0x8086/0x27c9(rev 0x2) are 0xe800
    Sep 2 00:43:51 localhost kernel[0]: USB caused wake event (EHCI)USBF: 10.812 Errata bits for controller 0x8086/0x27ca(rev 0x2) are 0xe800
    Sep 2 00:43:51 localhost kernel[0]: USBF: 10.815 Errata bits for controller 0x8086/0x27cb(rev 0x2) are 0xe800

    Thanks for the response. I found another thread for the same issue that stated I would need to RMA the device.

  • I have Java/J2ee  background , whether to go for EP or XI?

    Hello All,
    I am having 2 years of real time experience in Java/J2ee.
    I have already leaned ABAP and I don't have work experience in ABAP.
    Now I would like to go for SAP Netweaver.
    So,Please let me know whether to go for EP or XI?
    How will be the demand and requirement for EP and XI in the market now and in the future?
    Please give me suggestion. Thanks in advance.
    Regards,
    Cris

    Cris,
    I also have joined the NetWeaver Space[XI] from a plain J2EE background ..after 5 years into J2EE. I think your J2EE knowledge would be equally useful in both EP as well as XI. Offcourse , the spectrum of tasks you do in J2EE projects i.e. right from design to devlopment & deployment part might get narrowed as you wont be able to touch WebAS that easily as you could in a Weblogic / WebSphere based project.This is because the administration part is most of the times taken care by the basis team and your job would remain confined to design / development.
    Demand and requirement for EP and XI...wait and watch. I guess nobody can predict such things in todays world with ever changing technologies!!!

  • Could anyone tell me whether the ios7 for ipad with retina display comes with flash,compass and calculator!? Because mine has none!

    Could anyone tell me whether the ios7 for ipad with retina display comes with flash,compass and calculator!? Because mine has none!

    ravelvanto wrote:
    Could anyone tell me whether the ios7 for ipad with retina display comes with flash,compass and calculator!? Because mine has none!
    Hi ravelvanto,
    mine too (iPad 3/WiFi) hasn't this features.
    Especially the flash can't be realized because there is a simple lack of a flash light.
    Why there is no compass, calculator (I'm using the Wolfram App instead), or the weather app etc. I don't know...
    Best regards, mackevin

  • Trigger mail to MRP controller if Scheduled job for MRP fails

    How to configure Triggerring of mail to MRP controller if Scheduled job for MRP fails ?

    Dear Feby,
    Check this links to create a distribution list and to assign the same during background job scheduling in SM36 for the program
    RMMRP000.
    Re: Settings to be done for sending mail to external system
    Re: problem in background run
    Regards
    Mangalraj.S

  • Snes emulator for mountain lion with support for usb controller dongle

    Hi,
    I recently downloaded an snes emulator online and found that it does run the super nintendo game fine though it doesn't have support for the usb dongle for the controller. By any chance does anyone know a emular plug in or emulator for mountain lion that has this support for a usb joystick.

    Thanks for the reply. Still curious if Apple did right by their customers as the support rep implied that they would. I can't confirm either because I discovered tonight that I can't upgrade to Mountain Lion yet until Mariner Software decides to make one of their products compatible with 10.8.  Starting to think I need to find an alternative to their product.

  • To check whether searchterm maintained for   sales order

    hi ,
    i have to generate one alv report to check whether searchterm maintained for  sales order or not...
    can any one help me on this...
    thanks.

    Hi,
       The field VBAK-KTEXT can be of use to you.Refer tables :VBAK and VBAP.

  • I wanted to ask whether the camera for ipod touch comparable to a digital camera? if not are there apps available that can turn it into a digital camera? i want to buy an ipod touch and i like photography....what should i do?plz suggest

    i  wanted to ask whether the camera for ipod touch comparable to a digital camera? if not are there apps available that can turn it into a digital camera? i want to buy an ipod touch and i like photography....what should i do? plz suggest

    The iPod touch has a very rudimentary camera.  It has only a 0.6 MP resolution, no optical zoom, no flash, etc.   There is no app that can improve this as it is limited by the hardware. So it is not a replacement for a digital camera (nor even for an iPhone whose camera has a 5.0 MP resolution.

  • Enable the UAC settings for Domain Controller / Member servers and for end user systems

    Hi
    We are working on hardening the security for all Domain Controllers / Member Servers and end users systems. As part of it we would like to know the best practice for UAC settings for each of these servers. There are 8 settings related to UAC and as of now
    we configured just "User Account Control: Behavior of the elevation prompt for standard users" as disabled for the servers OU. Also not sure about other settings and how it affect the normal operations like installing Windows updates / applications
    through SCCM or manually on servers or end user systems and other stuffs.
    We are looking for experts opinion on this. Thanks in advance
    LMS

    Hi LMS,
    Would you please let us know the current situation? Just check if Martin’s suggestion was helpful for you.
    If any updates, please feel free to let us know.
    Just additional. Please refer to the
    User Account Control Grouping in the following article. It will provide some links about those different UAC settings. Please click those links and read related articles. In these articles, will provide
    Security considerations that may help you to configure those settings.
    Security Options
    http://technet.microsoft.com/en-us/library/jj852268.aspx
    Hope this helps.
    Best regards,
    Justin Gu

  • Musings: MVC Front Controller/Command and Controller Strategy

    Hi,
    I am currently taking my first shot at implementing the Front Controller pattern, the Command and Controller Strategy flavor, in Java. When applying the pattern, my chosen point of focus is achieving as much isolation as possible of Client-specific implementation details from the rest of the framework (Web-based framework Clients, Swing-based framework Clients, queueing-based framework Clients, etc.) However, I am running into a lot of (apparent?) inconsistencies when it comes to CCS discussions "out there", so I have a feeling that perhaps I have misunderstood the Front Controller/Command and Controller Strategy pattern. Maybe the MVC gurus out there would have some thoughts on the matter.
    My issues:
    1.) Some CCS discussions seem to assign View presentation (sometimes called "dispatch", or "rendering", or "forwarding"?) to an ApplicationController. It seems puzzling to me, since only a concrete FrontController should include any knowledge of a concrete View structure. Shouldn't only a FrontController perform a logical-to-physical resource mapping, thus encapsulating knowledge whether a particular View is a separate, stand-alone Web page or a compound, argument-driven Swing object, and how to "present it" (by either redirecting to a Web page, or bringing a particular Swing object into the foreground)?
    2.) Some CCS discussions seem to introduce Client-specific implementation details at the ApplicationController level, for example "HTTP requests" or "HTTP responses". It seems puzzling to me, since I feel that every part of the framework, except for a concrete FrontController, should be completely independent of the nature of a Client making a request. Instead, I created a generic Request object w/arguments and have a concrete FrontController translate any client-specific details into such a generic Request, before delegating to an ApplicationController.
    3.) In the light of the (2.) above, I am not sure what constitutes a "response" from an ApplicationController back to a FrontController. It seems to me that the only universal "response" is a LogicalViewEnumeration: what View to present once a command has been completed, in many cases a "don't care", or a "show the requestor", or a "show a home page" (not every request has to result in changing a View). Well, perhaps a LogicalViewEnumeration as well as possible View arguments (?).
    4.) In the light of the (3.) above, I suspect that any failures in Request delegation, or Command execution, should be perhaps propagated back to a FrontController by exceptions only, since, say, a WebFrontController might want to show a click-through error page, when a SwingFrontController might prefer to show an error dialog box, a LogicalErrorViewEnumeration might not make sense at all in the context of a particular Client, for example a queueing Client.
    5.) In the light of the (4.) above, there is the question of an appropriate Request interface (into an ApplicationController), an appropriate Response interface (back into a FrontController), as well as an appropriate ViewArguments interface (into a FrontController and later into a View). The problem with generic Requests is that they can be created with nonsensical argument combinations, so shouldn't Requests be abstract and force proper arguments in concrete subclasses, through explicit constructors (in a sense, degenerate Commands)? The problem with Responses and ViewArguments is that... well, I have not found any formal discussion anywhere as to what those should look like. In most samples I have encountered, Responses include Client-specific implementation details, as mentioned in (2.), above.
    6.) Some CCS discussions seem to introduce a Flow Manager at the ApplicationController level. It seems puzzling to me, since the whole point of the Command and Controller Strategy flavor seems to be centralization of business logic execution within self-contained Command objects. Shouldn't Requests get associated with Handlers (objects capable of actually carrying out Requests) and transformed into Commands inside an ApplicationController, thus Commands themselves return appropriate LogicalViewEnumeration back to an ApplicationController, back to a FrontController? Let's consider a ShowMyShippingAddress request coming into the framework: unless such a Request is eventually treated as a Command returning a particular LogicalViewEnumeration, it is suddenly a Flow Manager "acting" as a business logic driver. I guess the question here is: except for a few special cases handled by a particular ApplicationController (authentication, error conditions, default behavior, etc.), should flow management be considered stand-alone, or always delegated to Commands?
    7.) Some CCS discussions seem to include an extra Request argument that specifies an ApplicationController to use (Request.Action="create", Request.Controller="account", Request.Username="me-me-me"), instead of using a Router inside of a FrontController to resolve to a particular ApplicationController through a generic action (Request.Action="createAccount", Request.Username="me-me-me"). I am not sure about the reason for such a design decision: why should a Client or a FrontController be allowed to concern itself with an implementation-level structure of the framework? Wouldn't any framework state -dependent ApplicationController resolution issues be best handled inside a Router, used by a FrontController to resolve [obtain] an appropriate ApplicationController, thus preventing Clients from ever forcing the framework into a possibly inconsistent behavior?
    Any comments appreciated...
    Thanks,
    Gary

    gniemcew wrote:
    1.) Some CCS discussions seem to assign View presentation (sometimes called "dispatch", or "rendering", or "forwarding"?) to an ApplicationController. It seems puzzling to me, since only a concrete FrontController should include any knowledge of a concrete View structure. Shouldn't only a FrontController perform a logical-to-physical resource mapping, thus encapsulating knowledge whether a particular View is a separate, stand-alone Web page or a compound, argument-driven Swing object, and how to "present it" (by either redirecting to a Web page, or bringing a particular Swing object into the foreground)?It is hard to tell without reading the actual discussion, but my guess is that the posters were either conflating or being loose with the distinction between a FrontController and an ApplicationController. The former is (normally) intimately tied to the actual view being used (HTTP, Swing, etc.) whereas the ApplicationController typically is not. Both are involved in dispatch and event processing. The former normally renders a view whereas the latter does not.
    gniemcew wrote:
    2.) Some CCS discussions seem to introduce Client-specific implementation details at the ApplicationController level, for example "HTTP requests" or "HTTP responses". It seems puzzling to me, since I feel that every part of the framework, except for a concrete FrontController, should be completely independent of the nature of a Client making a request. Instead, I created a generic Request object w/arguments and have a concrete FrontController translate any client-specific details into such a generic Request, before delegating to an ApplicationController.Generic is fine. However, you can become generic to the point where your Request and Response interfaces are only acting as "marker" interfaces (think of java.io.Serializable). Writing a truly generic controller is possible, but personally, I have never found the effort justified.
    gniemcew wrote:
    3.) In the light of the (2.) above, I am not sure what constitutes a "response" from an ApplicationController back to a FrontController. It seems to me that the only universal "response" is a LogicalViewEnumeration: what View to present once a command has been completed, in many cases a "don't care", or a "show the requestor", or a "show a home page" (not every request has to result in changing a View). Well, perhaps a LogicalViewEnumeration as well as possible View arguments (?).A given service (if you ascribe to SOA) should be the fundamental unit in your architectural design. A good application controller would be responsible for determining how to dispatch a given Command. Whether a Command pattern is used or whether service methods are invoked directly from your FrontController, the ApplicationController should enforce common service aspects. These include authentication, authorization, auditing, orchestration, validation, logging, error handling, just to name a few.
    The ApplicationController should ideally offload these aspects from a given service. The service would indicate how the aspects are to be applied (e.g., strong authentication required, x role required, fetching of existing process state, etc.) This allows services to be developed more quickly and to have these critical aforementioned aspects developed and tested centrally.
    Your FrontController, in contrast, is responsible for transforming whatever input it is designed to receive (HTTP form data posts, XML-RPC, etc.) and ensure that it honors the contract(s) that the ApplicationController establishes. There are no cut-and-dry decisions though about when a given piece of functionality should be ApplicationController or FrontController. Take error handling. Should I emit just a generic ServiceException or allow the FrontController to decide what to do with a more concrete checked exception? (The FrontController, in any case, should present the error to the user in a manner dictated by the protocol it serves).
    gniemcew wrote:
    4.) In the light of the (3.) above, I suspect that any failures in Request delegation, or Command execution, should be perhaps propagated back to a FrontController by exceptions only, since, say, a WebFrontController might want to show a click-through error page, when a SwingFrontController might prefer to show an error dialog box, a LogicalErrorViewEnumeration might not make sense at all in the context of a particular Client, for example a queueing Client.See above. Yes. However, the ApplicationController could easily 'hide' details about the failure. For example, any number of exceptions being mapped to a generic DataAccessException or even more abstractly to a ServiceFailureException. The ApplicationController could indicate whether the failure was recoverable and/or populate information necessary to speed up production support (e.g., mapping exceptions to error codes and/or providing a primary key in an error audit log table for support to reference). A given FrontController would present that information to the user in the method that makes sense (e.g., error dialog for Swing, error page for HTML, etc.)
    gniemcew wrote:
    5.) In the light of the (4.) above, there is the question of an appropriate Request interface (into an ApplicationController), an appropriate Response interface (back into a FrontController), as well as an appropriate ViewArguments interface (into a FrontController and later into a View). The problem with generic Requests is that they can be created with nonsensical argument combinations, so shouldn't Requests be abstract and force proper arguments in concrete subclasses, through explicit constructors (in a sense, degenerate Commands)? The problem with Responses and ViewArguments is that... well, I have not found any formal discussion anywhere as to what those should look like. In most samples I have encountered, Responses include Client-specific implementation details, as mentioned in (2.), above.See comment on marker interfaces above. Nothing, however, stops you from requiring a certain sub-type in a given service method. You can still pass in the interface and validate the proper type by an assert statement (after all, in the vast majority of situations, the proper service method should get the proper instance of a given Request object). IMO, the FrontController would create the Command instance which would be passed to the ApplicationController which would dispatch and invoke the proper service method. A model response would be received by the FrontController which would then render the appropriate view.
    gniemcew wrote:
    6.) Some CCS discussions seem to introduce a Flow Manager at the ApplicationController level. It seems puzzling to me, since the whole point of the Command and Controller Strategy flavor seems to be centralization of business logic execution within self-contained Command objects. Shouldn't Requests get associated with Handlers (objects capable of actually carrying out Requests) and transformed into Commands inside an ApplicationController, thus Commands themselves return appropriate LogicalViewEnumeration back to an ApplicationController, back to a FrontController? Let's consider a ShowMyShippingAddress request coming into the framework: unless such a Request is eventually treated as a Command returning a particular LogicalViewEnumeration, it is suddenly a Flow Manager "acting" as a business logic driver. I guess the question here is: except for a few special cases handled by a particular ApplicationController (authentication, error conditions, default behavior, etc.), should flow management be considered stand-alone, or always delegated to Commands?There are distinct kinds of flow management. For example, orchestration (or BPM) is properly at either the service or ApplicationController layers. However, determining which view to display is properly at the FrontController layer. The ApplicationController should receive a Command (with a populate Request) and return that Command (with a populated Response). Both the Request and Response are fundamentally model classes (within MVC). The FrontController is responsible for populating the Request and/or Command and rendering the Response and/or Command. Generic error handling is usually centralized for both controllers.
    gniemcew wrote:
    7.) Some CCS discussions seem to include an extra Request argument that specifies an ApplicationController to use (Request.Action="create", Request.Controller="account", Request.Username="me-me-me"), instead of using a Router inside of a FrontController to resolve to a particular ApplicationController through a generic action (Request.Action="createAccount", Request.Username="me-me-me"). I am not sure about the reason for such a design decision: why should a Client or a FrontController be allowed to concern itself with an implementation-level structure of the framework? Wouldn't any framework state -dependent ApplicationController resolution issues be best handled inside a Router, used by a FrontController to resolve [obtain] an appropriate ApplicationController, thus preventing Clients from ever forcing the framework into a possibly inconsistent behavior?I am not 100% sure of what you are getting at here. However, it seems to be the method by which commands are dispatched. They are in effect allowing a FrontController to dictate which of n ApplicationControllers should receive the request. If we allow a FrontController to directly invoke a service method, then the ApplicationController is simply a centralized framework that should always be invoked for each service method (enforced via AOP or some other mechanism). If there is a single, concrete ApplicationController which handles dispatch, then all FrontControllers communicate directly with that instance. It is really just a design decision (probably based on your comfort level with concepts like AOP that allow the ApplicationController to exist solely behind the scenes).
    I might have totally missed your questions, but those are my thoughts on a Monday. Best of luck.
    - Saish

  • Advice for a PC configuration upgrade for Adobe Creative Cloud, please?

    Hi everyone,
    For the moment I have an old PC (bought in April 2008) and maybe if you eventually help me I could have a more powerful machine. I am asking you five questions at then end of this post, so if someone can reply it would help me and be greatful.
    Here is the resume of the configuration of my desktop
    --------[ Operating System ]---------------------------------------------------------------------------------------- ----
        Operating System Properties:
          OS Name                                           Microsoft Windows 8.1 Professional
          OS Language                                       English (United Kingdom)
          OS Installer Language                             English (United Kingdom)
          OS Kernel Type                                    Multiprocessor Free (64-bit)
          OS Version                                        6.3.9600.16452 (Win8.1 RTM)
          OS Service Pack                                   -
          OS Root                                           C:\WINDOWS
          Components Version:
          Common Controls                                   6.16
          Windows Mail                                      6.3.9600.16384 (winblue_rtm.130821-1623)
          Windows Media Player                              12.0.9600.16384 (winblue_rtm.130821-1623)
          Windows Messenger                                 -
          MSN Messenger                                     -
          Internet Information Services (IIS)               -
          .NET Framework                                    4.0.30319.33440 built by: FX45W81RTMREL
          Novell Client                                     -
          DirectX                                           DirectX 11.0
          OpenGL                                            6.3.9600.16384 (winblue_rtm.130821-1623)
          ASPI                                              -
        Operating System Features:
          Debug Version                                     No
          DBCS Version                                      No
          Domain Controller                                 No
          Security Present                                  No
          Network Present                                   Yes
          Remote Session                                    No
          Safe Mode                                         No
          Slow Processor                                    No
          Terminal Services                                 Yes
    --------[ Motherboard ]---------------------------------------------------------------------------------------- ---------
        Motherboard Properties:
          Motherboard ID                                    06/19/2009-P35-ICH9-6A89OG0PC-00
          Motherboard Name                                  Gigabyte GA-EP35-DS4
        Front Side Bus Properties:
          Bus Type                                          Intel AGTL+
          Bus Width                                         64-bit
          Real Clock                                        333 MHz (QDR)
          Effective Clock                                   1333 MHz
          Bandwidth                                         10667 MB/s
        Memory Bus Properties:
          Bus Type                                          Dual DDR2 SDRAM
          Bus Width                                         128-bit
          DRAM:FSB Ratio                                    12:10
          Real Clock                                        400 MHz (DDR)
          Effective Clock                                   800 MHz
          Bandwidth                                         12800 MB/s
        Chipset Bus Properties:
          Bus Type                                          Intel Direct Media Interface
        Motherboard Physical Info:
          CPU Sockets/Slots                                 1 LGA775
          Expansion Slots                                   2 PCI, 3 PCI-E x1, 2 PCI-E x16
          RAM Slots                                         4 DDR2 DIMM
          Integrated Devices                                Audio, Gigabit LAN, IEEE-1394
          Form Factor                                       ATX
          Motherboard Size                                  240 mm x 300 mm
          Motherboard Chipset                               P35
          Extra Features                                    Dynamic Energy Saver, SATA-II, RAID
        Motherboard Manufacturer:
          Company Name                                      Gigabyte Technology Co., Ltd.
    --------[ CPU ]---------------------------------------------------------------------------------------- -----------------
        CPU Properties:
          CPU Type                                          DualCore Intel Core 2 Duo E8400, 3000 MHz (9 x 333)
          CPU Alias                                         Wolfdale
          CPU Stepping                                      C0
          Instruction Set                                   x86, x86-64, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1
          Original Clock                                    3000 MHz
          Min / Max CPU Multiplier                          6x / 9x
          Engineering Sample                                No
          L1 Code Cache                                     32 KB per core
          L1 Data Cache                                     32 KB per core
          L2 Cache                                          6 MB  (On-Die, ECC, ASC, Full-Speed)
        CPU Physical Info:
          Package Type                                      775 Contact FC-LGA8
          Package Size                                      37.5 mm x 37.5 mm
          Transistors                                       410 million
          Process Technology                                45 nm, CMOS, Cu, High-K + Metal Gate
          Die Size                                          107 mm2
          Core Voltage                                      1.113 - 1.225 V
          I/O Voltage                                       1.113 - 1.225 V
          Typical Power                                     65 W @ 3.00 GHz
          Maximum Power                                     91.9 W @ 3.00 GHz
        CPU Manufacturer:
          Company Name                                      Intel Corporation
          Product Information                               http://ark.intel.com/search.aspx?q=Intel Core 2 Duo E8400
        Multi CPU:
          Motherboard ID                                    OEM00000 PROD00000000
          CPU #1                                            Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 3000 MHz
          CPU #2                                            Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 3000 MHz
        CPU Utilization:
          CPU #1 / Core #1                                  0 %
          CPU #1 / Core #2                                  0 %
    --------[ Windows Video ]---------------------------------------------------------------------------------------- -------
      [ NVIDIA Quadro 2000 ]
        Video Adapter Properties:
          Device Description                                NVIDIA Quadro 2000
          Adapter String                                    Quadro 2000
          BIOS String                                       Version 70.6.41.0.6
          Chip Type                                         Quadro 2000
          DAC Type                                          Integrated RAMDAC
          Driver Date                                       29/09/2013
          Driver Version                                    9.18.13.2739 - nVIDIA ForceWare 327.39
          Driver Provider                                   NVIDIA
          Memory Size                                       1 GB
        Installed Drivers:
          nvd3dumx                                          9.18.13.2739
          nvwgf2umx                                         9.18.13.2739
          nvwgf2umx                                         9.18.13.2739
          nvd3dum                                           9.18.13.2739 - nVIDIA ForceWare 327.39
          nvwgf2um                                          9.18.13.2739
          nvwgf2um                                          9.18.13.2739
        Video Adapter Manufacturer:
          Company Name                                      NVIDIA Corporation
      [ NVIDIA Quadro 2000 ]
        Video Adapter Properties:
          Device Description                                NVIDIA Quadro 2000
          Adapter String                                    Quadro 2000
          BIOS String                                       Version 70.6.41.0.6
          Chip Type                                         Quadro 2000
          DAC Type                                          Integrated RAMDAC
          Driver Date                                       29/09/2013
          Driver Version                                    9.18.13.2739 - nVIDIA ForceWare 327.39
          Driver Provider                                   NVIDIA
          Memory Size                                       1 GB
        Installed Drivers:
          nvd3dumx                                          9.18.13.2739
          nvwgf2umx                                         9.18.13.2739
          nvwgf2umx                                         9.18.13.2739
          nvd3dum                                           9.18.13.2739 - nVIDIA ForceWare 327.39
          nvwgf2um                                          9.18.13.2739
          nvwgf2um                                          9.18.13.2739
        Video Adapter Manufacturer:
          Company Name                                      NVIDIA Corporation
          Product Information                               http://www.nvidia.com/page/products.html
    --------[ Physical Drives ]---------------------------------------------------------------------------------------- -----
    HDDs :
    . 2 HDDs 2 x 1 TB SATA-II RAID 0 for video editing, the OS and software
    . 1 HDD 2 TB SATA-II for backups
    . 1 HDD 2 TB SATA-III for backups off site + Archive
      [ Drive #1 - Intel   Raid 0 Volume (1863 GB) ]
        #1 (Active)      NTFS                                                             1 MB      350 MB
        #2               NTFS             C:                                            351 MB  1907380 MB
      [ Drive #2 - WDC WD20EZRX-00D8PB0 (1863 GB) ]
        #1               MS Reserved                                                      0 MB      128 MB
        #2               Basic Data       G: (Archives)                                 129 MB  1907600 MB
      [ Drive #3 - Hitachi HDS722020ALA330 (1863 GB) ]
        #1               NTFS             D: (Backup)                                     1 MB  1907727 MB
    --------[ Memory ]---------------------------------------------------------------------------------------- --------------
        Physical Memory:
          Total                                             8190 MB
          Used                                              3334 MB
          Free                                              4856 MB
          Utilization                                       41 %
        Swap Space:
          Total                                             9470 MB
          Used                                              4131 MB
          Free                                              5340 MB
          Utilization                                       44 %
        Virtual Memory:
          Total                                             17661 MB
          Used                                              7465 MB
          Free                                              10196 MB
          Utilization                                       42 %
        Paging File:
          Paging File                                       C:\pagefile.sys
          Current Size                                      1280 MB
          Current / Peak Usage                              243 MB / 700 MB
          Utilization                                       19 %
        Physical Address Extension (PAE):
          Supported by Operating System                     Yes
          Supported by CPU                                  Yes
          Active                                            Yes
    --------[ SPD ]---------------------------------------------------------------------------------------- -----------------
      [ DIMM1: GeIL CL5-5-5  DDR2-800 ]
        Memory Module Properties:
          Module Name                                       GeIL CL5-5-5  DDR2-800
          Serial Number                                     None
          Manufacture Date                                  Week 44 / 2009
          Module Size                                       2 GB (2 ranks, 8 banks)
          Module Type                                       Unbuffered DIMM
          Memory Type                                       DDR2 SDRAM
          Memory Speed                                      DDR2-800 (400 MHz)
          Module Width                                      64 bit
          Module Voltage                                    SSTL 1.8
          Error Detection Method                            None
          Refresh Rate                                      Reduced (7.8 us), Self-Refresh
        Memory Timings:
          @ 400 MHz                                         5-5-5-15  (CL-RCD-RP-RAS) / 23-51-3-6-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 333 MHz                                         4-5-5-13  (CL-RCD-RP-RAS) / 20-43-3-5-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 266 MHz                                         3-4-4-10  (CL-RCD-RP-RAS) / 16-34-2-4-2-2  (RC-RFC-RRD-WR-WTR-RTP)
        Memory Module Features:
          Analysis Probe                                    Not Present
          FET Switch External                               Disabled
          Weak Driver                                       Supported
        Memory Module Manufacturer:
          Company Name                                      Golden Emperor International Ltd.
          Product Information                               http://www.geil.com.tw/products
      [ DIMM2: GeIL CL5-5-5DDR2800  5 ]
        Memory Module Properties:
          Module Name                                       GeIL CL5-5-5DDR2800  5
          Serial Number                                     00000005h (83886080)
          Module Size                                       2 GB (2 ranks, 8 banks)
          Module Type                                       Unbuffered DIMM
          Memory Type                                       DDR2 SDRAM
          Memory Speed                                      DDR2-800 (400 MHz)
          Module Width                                      64 bit
          Module Voltage                                    SSTL 1.8
          Error Detection Method                            None
          Refresh Rate                                      Reduced (7.8 us), Self-Refresh
        Memory Timings:
          @ 400 MHz                                         5-5-5-18  (CL-RCD-RP-RAS) / 23-51-3-6-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 266 MHz                                         4-4-4-12  (CL-RCD-RP-RAS) / 16-34-2-4-2-2  (RC-RFC-RRD-WR-WTR-RTP)
          @ 200 MHz                                         3-3-3-9  (CL-RCD-RP-RAS) / 12-26-2-3-2-2  (RC-RFC-RRD-WR-WTR-RTP)
        Memory Module Features:
          Analysis Probe                                    Not Present
          FET Switch External                               Disabled
          Weak Driver                                       Supported
        Memory Module Manufacturer:
          Company Name                                      Golden Emperor International Ltd.
          Product Information                               http://www.geil.com.tw/products
      [ DIMM3: GeIL CL5-5-5  DDR2-800 ]
        Memory Module Properties:
          Module Name                                       GeIL CL5-5-5  DDR2-800
          Serial Number                                     None
          Manufacture Date                                  Week 44 / 2009
          Module Size                                       2 GB (2 ranks, 8 banks)
          Module Type                                       Unbuffered DIMM
          Memory Type                                       DDR2 SDRAM
          Memory Speed                                      DDR2-800 (400 MHz)
          Module Width                                      64 bit
          Module Voltage                                    SSTL 1.8
          Error Detection Method                            None
          Refresh Rate                                      Reduced (7.8 us), Self-Refresh
        Memory Timings:
          @ 400 MHz                                         5-5-5-15  (CL-RCD-RP-RAS) / 23-51-3-6-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 333 MHz                                         4-5-5-13  (CL-RCD-RP-RAS) / 20-43-3-5-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 266 MHz                                         3-4-4-10  (CL-RCD-RP-RAS) / 16-34-2-4-2-2  (RC-RFC-RRD-WR-WTR-RTP)
        Memory Module Features:
          Analysis Probe                                    Not Present
          FET Switch External                               Disabled
          Weak Driver                                       Supported
        Memory Module Manufacturer:
          Company Name                                      Golden Emperor International Ltd.
          Product Information                               http://www.geil.com.tw/products
      [ DIMM4: GeIL CL5-5-5DDR2800  5 ]
        Memory Module Properties:
          Module Name                                       GeIL CL5-5-5DDR2800  5
          Serial Number                                     00000005h (83886080)
          Module Size                                       2 GB (2 ranks, 8 banks)
          Module Type                                       Unbuffered DIMM
          Memory Type                                       DDR2 SDRAM
          Memory Speed                                      DDR2-800 (400 MHz)
          Module Width                                      64 bit
          Module Voltage                                    SSTL 1.8
          Error Detection Method                            None
          Refresh Rate                                      Reduced (7.8 us), Self-Refresh
        Memory Timings:
          @ 400 MHz                                         5-5-5-18  (CL-RCD-RP-RAS) / 23-51-3-6-3-3  (RC-RFC-RRD-WR-WTR-RTP)
          @ 266 MHz                                         4-4-4-12  (CL-RCD-RP-RAS) / 16-34-2-4-2-2  (RC-RFC-RRD-WR-WTR-RTP)
          @ 200 MHz                                         3-3-3-9  (CL-RCD-RP-RAS) / 12-26-2-3-2-2  (RC-RFC-RRD-WR-WTR-RTP)
        Memory Module Features:
          Analysis Probe                                    Not Present
          FET Switch External                               Disabled
          Weak Driver                                       Supported
        Memory Module Manufacturer:
          Company Name                                      Golden Emperor International Ltd.
          Product Information                               http://www.geil.com.tw/products
    --------[ Windows Audio ]---------------------------------------------------------------------------------------- -------
        midi-out.0   0001 001B  Microsoft GS Wavetable Synth
        mixer.0      0001 FFFF  Speakers (5- High Definition Au
        mixer.1      0001 FFFF  Digital Audio (S/PDIF) (5- High
        mixer.2      0001 FFFF  W240D DVI (4- High Definition A
        mixer.5      0001 FFFF  Microphone (5- High Definition
        wave-in.0    0001 FFFF  Microphone (5- High Definition
        wave-in.1    0001 FFFF  Digital Audio (S/PDIF) (5- High
        wave-in.2    0001 FFFF  Line In (5- High Definition Aud
        wave-out.0   0001 FFFF  Speakers (5- High Definition Au
        wave-out.1   0001 FFFF  Digital Audio (S/PDIF) (5- High
        wave-out.2   0001 FFFF  W240D DVI (4- High Definition A
    --------[ PCI / PnP Audio ]---------------------------------------------------------------------------------------- -----
        nVIDIA HDMI/DP @ nVIDIA GF106 - High Definition Audio Controller                  PCI
        nVIDIA HDMI/DP @ nVIDIA GF106 - High Definition Audio Controller                  PCI
        nVIDIA HDMI/DP @ nVIDIA GF106 - High Definition Audio Controller                  PCI
        nVIDIA HDMI/DP @ nVIDIA GF106 - High Definition Audio Controller                  PCI
        Realtek ALC889A @ Intel 82801IB ICH9 - High Definition Audio Controller [A-2]     PCI
    --------[ HD Audio ]---------------------------------------------------------------------------------------- ------------
      [ Intel 82801IB ICH9 - High Definition Audio Controller [A-2] ]
        Device Properties:
          Device Description                                Intel 82801IB ICH9 - High Definition Audio Controller [A-2]
          Device Description (Windows)                      Contrôleur High Definition Audio
          Bus Type                                          PCI
          Bus / Device / Function                           0 / 27 / 0
          Device ID                                         8086-293E
          Subsystem ID                                      1458-A022
          Revision                                          02
          Hardware ID                                       PCI\VEN_8086&DEV_293E&SUBSYS_A0221458&REV_02
        Device Manufacturer:
          Company Name                                      Intel Corporation
          Product Information                               http://www.intel.com/products/chipsets
      [ Realtek ALC889A ]
        Device Properties:
          Device Description                                Realtek ALC889A
          Device Description (Windows)                      Périphérique High Definition Audio
          Device Type                                       Audio
          Bus Type                                          HDAUDIO
          Device ID                                         10EC-0885
          Subsystem ID                                      1458-A002
          Revision                                          1001
          Hardware ID                                       HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_1458A002&REV_1001
        Device Manufacturer:
          Company Name                                      Realtek Semiconductor Corp.
          Product Information                               http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PNid=8&PFid=14&Level=3&Conn= 2
      [ nVIDIA GF106 - High Definition Audio Controller ]
        Device Properties:
          Device Description                                nVIDIA GF106 - High Definition Audio Controller
          Device Description (Windows)                      Contrôleur High Definition Audio
          Bus Type                                          PCI
          Bus / Device / Function                           1 / 0 / 1
          Device ID                                         10DE-0BE9
          Subsystem ID                                      103C-084A
          Revision                                          A1
          Hardware ID                                       PCI\VEN_10DE&DEV_0BE9&SUBSYS_084A103C&REV_A1
        Device Manufacturer:
          Company Name                                      NVIDIA Corporation
      [ nVIDIA HDMI/DP ]
        Device Properties:
          Device Description                                nVIDIA HDMI/DP
          Device Description (Windows)                      Périphérique High Definition Audio
          Device Type                                       Audio
          Bus Type                                          HDAUDIO
          Device ID                                         10DE-0011
          Subsystem ID                                      10DE-0101
          Revision                                          1001
          Hardware ID                                       HDAUDIO\FUNC_01&VEN_10DE&DEV_0011&SUBSYS_10DE0101&REV_1001
        Device Manufacturer:
          Company Name                                      NVIDIA Corporation
      [ nVIDIA HDMI/DP ]
        Device Properties:
          Device Description                                nVIDIA HDMI/DP
          Device Description (Windows)                      Périphérique High Definition Audio
          Device Type                                       Audio
          Bus Type                                          HDAUDIO
          Device ID                                         10DE-0011
          Subsystem ID                                      10DE-0101
          Revision                                          1001
          Hardware ID                                       HDAUDIO\FUNC_01&VEN_10DE&DEV_0011&SUBSYS_10DE0101&REV_1001
        Device Manufacturer:
          Company Name                                      NVIDIA Corporation
      [ nVIDIA HDMI/DP ]
        Device Properties:
          Device Description                                nVIDIA HDMI/DP
          Device Description (Windows)                      Périphérique High Definition Audio
          Device Type                                       Audio
          Bus Type                                          HDAUDIO
          Device ID                                         10DE-0011
          Subsystem ID                                      10DE-0101
          Revision                                          1001
          Hardware ID                                       HDAUDIO\FUNC_01&VEN_10DE&DEV_0011&SUBSYS_10DE0101&REV_1001
        Device Manufacturer:
          Company Name                                      NVIDIA Corporation
      [ nVIDIA HDMI/DP ]
        Device Properties:
          Device Description                                nVIDIA HDMI/DP
          Device Description (Windows)                      Périphérique High Definition Audio
          Device Type                                       Audio
          Bus Type                                          HDAUDIO
          Device ID                                         10DE-0011
          Subsystem ID                                      10DE-0101
          Revision                                          1001
          Hardware ID                                       HDAUDIO\FUNC_01&VEN_10DE&DEV_0011&SUBSYS_10DE0101&REV_1001
        Device Manufacturer:
          Company Name                                      NVIDIA Corporation
    October 26th, 2012 Microsoft told me with "Microsoft Update Advisor" that I could upgraded my OS from Windows 7 Pro 64 bits to Windows 8 Pro 64 bits and after one year with another "Microsoft Upgrade Advisor" Microsoft told me again to upgrade my OS from Windows 8 Pro 64 bits to Windows 8.1 Pro 64 bits, but Gigabyte does not give the drivers on their website for my motherboard neither for Windows 8 and neither for Windows 8.1 and the system is however liable.
    If I believe Gigabyte I need to purchase a new motherboard and probably a new CPU and new RAM.
    1) Do you agree with Gigabyte or with Microsoft?
    2) If we believe Gigabyte, so can you tell me what king of CPU and motherboard to choose for video editing and video encoding, please?
    In the past, I had followed Adobe advices to use a Nvidia Quadro 2000 video card and HDDs in RAID 0 for video editing and video encoding.
    Moreover, Microsoft recommends to use a SSD for Windows 8.1.
    3) So, do you think I really need a SSD, with which capacity (256 or 512 GB ?) and which brand?
    4) A SSD for the OS and software and HDDs in RAID 0 for video editing?
    I edit HD (1600 x 1080 pixels) and I plan a budget between 450 and 650 $ for upgrading my PC.
    Maybe I can only buy one new motherboard for 200 $, keeping my CPU and my RAM and buy a SSD 480 GB for 333 $ (total 200 + 333 = 533 $).
    5) Do you agree with me for buying just only a motherboard and a SSD ?
    Thank you in advance if someone can help me.
    Otherwise my configuration seems to comply with http://www.adobe.com/products/creativecloud/tech-specs.html I have only a doubt for the sound.
    Best regards
    PS: the names of actual companies and products mentioned herein may be the trademarks of their respective owners.

    Hello Isidore,
    I can answer questions 3 and 4, as I have that sort of setup.
    3.) No, you don't really need an SSD, but I would certainly recommend that you buy one.  You'll notice a huge difference in the amount of time it takes to boot.  I bought the OCZ Vertex 3 (120GB) a while back, and it's very fast.  Whether or not you should get one just depends on whether the speed is worth it to you, but if I were you, I would.
    As for the size, that depends on exactly what you'll use it for.  See number 4 below.
    4.) Yes, that's my setup.  The SSD is my primary drive, and my HDD is for everything else.  Here's basically how I have everything setup:
    When I finish a day of shooting, I copy all my footage into a special folder (I named it "IMPORT" since I use it often) on my SSD.  I do this because the clips load much faster in Prelude and Premiere Pro.  Then, after I finish and export the project, I move all the original files onto my HDD.  I would still do this even I had a larger SSD, because it's always good to keep your primary drives clean.
    I also set the render and cache directories to those that I create on my HDD, because for longer projects, my SSD would fill up quickly, so that's why you may want to consider buying a larger SSD (even though 128GB would probably work just fine).
    I hope this helped a little!
    ~Josh

  • Difference between MVC & Front- Controller

    Hi All,
    could anyone help me out in differenciating the MVC & Front controller patterns.
    regards
    Karthik

    When should an application use the Front Controller
    patern and when should they use MVC? This boils down to scope of the problem domain and requirements.
    The Front Controller seems largely like a subset of
    MVC.Yes.
    Is there a situation where the Front Controller
    is more advantageous to use than MVC?Where its lighter weight pays off, i.e where you do not have a conventional model, e.g with streaming prototcol handlers or with fast readers. MVC is most useful for a N-Tier J2ee application offering CRUD type functionality.

  • Comparison between WebDynpro for ABAP vs. WebDynpro for Java ??

    Hi,
       Can someone tell me when should we go for WebDynpro for ABAP and when WebDynpro for Java. Is there any link where SAP recommends the one for the other.
    Thanks in advance
    Regards
    Mukesh

    Hi Mukesh,
    Both are having its own strengths!! )
    I think it all depends on your project requirement and the availabel resources.
    If the developer is good in OOPs ABAP then he must go for Web Dynpro ABAP. But if anyone is good in JAVA then that person should go for Web Dynpro JAVA.
    *In Short almost all Features supported in webdynpro ABAP are also Possible in webdynpro Java.
    1] Webdynpro Java
    Supports,
    webservice
    RFC Models
    Accessing Portal information in Java
    Easy sending E-mail
    Strictly follows MVC architecture which seperate Business logic and Process flow.
    Webdynpro Java is webbased programming model to develop SAP Applications.
    Easy to learn
    Easy to integrate in Enter prise portals.
    Dynanamic Programming
    *Easy access to R/3 Via RFC technology (Models)
    2] Web Dynpro ABAP
    As the name suggests Web Dynpro for ABAP uses exactly the same meta model as its cousin Web Dynpro for Java. A Web Dynpro component, a Web Dynpro view, a Web Dynpro model, a Web Dynpro controller have the same semantics both for ABAP and Java. The main difference is the designtime environment, the development infrastructure and the runtime environment.
    The designtime environment is properly embedded in the ABAP Workbench where Web Dynpro artifacts are simply a new category like BSP applications or classical dynpro based applications before. Also no surprises regarding the development infrastructure. The correction and transport system keeps track on all changes that are done, versions them and helps to propagate the Web Dynpro application from development to production like you would do with ordinary BSP or dynpro-based applications.
    Last not least the execution platform is the ABAP server that produces application content ready to be integrated in the NetWeaver Portal seamlessly. Features like portal eventing can be used between applications written in ABAP or applications developed with Java.
    Hope this helps and solve your Problem
    Cheers,
    Darshna.

Maybe you are looking for

  • Can't connect to internet on my n97mini. Please he...

    I bought a new n97mini (unlocked) through my local optus dealer but can't connect to the net. Im currently with vodafone but was told by the dealer that I would have no problems with this sim in the phone. Is there something I need to change on the p

  • New Plug-In for Acrobat: 3D Bill-of-Materials

    Hello everyone! We at vpr-solutions are thinking of developing an Adobe Acrobat Plug-In which allows users to create 3D-PDF Bill-Of-Materials with just a few mouse clicks. The outcome would be an interactive 3D-PDF, similar to this: http://vpr-soluti

  • Problem with Interaction edits to subtitle

    Can't select the subtitle to add instructions in Widget Properties. Updated to Captivate 6.0.1.240 that solved other edit problems, however still can't select and edit the subtitle of the Accordian interaction. Any suggestions?

  • IPhoto book - Never shipped

    How frustrating. I ordered my first printed book from Apple and it supposedly shipped on July 13 to be delivered on July 17. I paid for express shipping. On July 17, I checked the tracking number and the only information was that the order was electr

  • Fault Reporting and Repair Time

    Is it me or is the fault reporting number for BT useless? I realised our phone line wasn't working at about 20:00hrs in the evening. I live in an area with no mobile signal so drove the few miles needed to get a mobile signal and called 0800800151 to