On 4/5/06, Pathogenix <[EMAIL PROTECTED]> wrote: > > > I always create own classes that a running as AJAX data access layer > > to the business logic. I never use methods directly in pages. > > So you've a facade class which passes requests through to your data > access layer, or do you directly expose your DAL classes to Ajax? I'm > planning on writing a short app in the next month or so, and I want to > go with Ajax.Net from the ground up, so I'm just trying to work out > some best practices.
In most web projects the objects that I get from the database or from other different locations are more complex, maybe too complex for my little JavaScript that I need. And that is the reason why I add another layer between. I can change the DAL in theses classes if I want, never have to change my JavaScript code. Because JavaScript code is not compiled I do not get any error message, only when running the web application. This is the reason why I want to have a fixed contract between JavaScript and the web server. > > Do you really have this often that something is not working because of > > switching to a newer version? Would be nice to get such feedbacks > > earlier because I use the library in different projects and never had > > such problems > > Admittedly I've used three different versions in two days :) I'm > probably just being grumpy, but you were returning Decimal.GetBits() > and you replaced that with a better Decimal parser (thanks for that!), > I switched over to that, and my enums were being formattted differently > as well, returned as simple int's rather than a separate object (again > - I like the change...) so I nipped through all my code and fixed that, > then discovered that I couldn't post requests to the server because > you'd changed (I assume) the default toJSON so that I had to explictly > parse strings as ints. Again, I understand the change, I like the > change, but it's a bit overwhelming. Then I come online to say > Whooooaaa slow down, dude - and there's another new version released. Ok, you are right, as you may seen in the latest beta I have added a new section in web.config called oldStyle. There I will put the old style working features in the future, so if I make a big change I will put an option there to have it like it was. In the latest ZIP file I put also a readme.txt where you can find more details on the changes. > > I'm running source safe since beginning of this year, since I got the > > MVP status. > > Source Unsafe? Fair enough, I was sort of hoping for a subversion repo, > but I'm a weirdo. I will put the source code online from time to time to let others have a look on it... > > Yes, if you have patches, changes or new ideas, send me the files and > > I will check if they fit in the library. Would be nice to get help, of > > course! > > Well I feel like I owe you, drop me a line if you ever need a hand with > docs, samples, etc. It'd be the least I could do. Did I mention that I > love your framework? I'll have a think about the Generic serializer - > since you're building .Net 2.0 anyway, it sort of makes sense to take > advantage of it. Would be great if you have some time on the generic stuff!!! Regards, Michael > > Cheers, > > -- flinky wisty pomm > > > > > -- Kind regards, Michael Schwarz Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://www.schwarz-interactive.de/ mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
