Hi Gene,
Gene Amtower wrote: > > I will need to insure that a nocache parameter > is specified in the Oracle RPC procedure being called, and it should > process the requests as expected. That's a good point that I might have > overlooked at first, so I appreciate the heads-up on it. > > Is that what you're suggesting? > More or less: you may choose to ignore a "nocache" parameter in the server handler, use the appropriate "no-url-params-on-post" in the client request or avoid that tricky mixed-mode in your implementation: I'd suggest the last one, as: * Filtering "nocache" server-side will be prone errors if/when other unexpected GET parameters are used; * Use the "no-url-params-on-post" will be somehow specific to that specific server-mode. Note that none of this trickery would be needed in a perfect world (the "nocache" and similar are old workarounds to buggy proxies and other related network infrastructure issues, both at Internet and intranet levels. Regards, Helder -- View this message in context: http://www.nabble.com/Has-Anyone-Worked-on-an-Oracle-PL-SQL-RPC-Server-tp24112370p24147805.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
